Messages in this thread | | | Subject | Re: [PATCH] paravirt.h | From | Alan Cox <> | Date | Tue, 22 Aug 2006 22:36:17 +0100 |
| |
Ar Maw, 2006-08-22 am 12:17 -0700, ysgrifennodd Zachary Amsden: > Possibly an issue, but why would you ever want stacked paravirt-ops? > You're only talking to the hypervisor directly above you, and there is > only one of those.
Thankfully right now I can't think of a reason other than debugging when using hardware VMX
> > - If we boot patch inline code to get performance natively its almost > > impossible to then revert that.
> You can patch back over it. I've already implemented the locking and > repatching bits for VMI.
Ok that bit seemed pretty scary because you have to halt all the processors in a known state (which probably means in an IPI handler) before you patch. If you have code thats great.
Alan
- 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/
| |