Messages in this thread | | | Subject | Re: [patch] paravirt: isolate module ops | From | Arjan van de Ven <> | Date | Fri, 05 Jan 2007 18:07:09 -0800 |
| |
> > I would suggest a slightly different carving. For one, no TLB flushes. > If you can't modify PTEs, why do you need to have TLB flushes? And I > would allow CR0 read / write for code which saves and restores FPU state
no that is abstracted away by kernel_fpu_begin/end. Modules have no business doing that themselves
> - possibly even debug register access, although any code which touches > DRs could be doing something sneaky. I'm on the fence about that one.
lets not allow it at all
-- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |