Anthony Liguori wrote:
I don't see a compelling reason to paravirtualize earlier although I also don't see a compelling reason not too. I noticed that VMI hooks setup.c. It wasn't immediately obvious why it was hooking there but perhaps it worthwhile to have a common hook? I suspect VMI and KVM will have a similar model for startup.
VMI would like to engage after kernel early facilities are available, so command line arguments have been processed. It is desirable to activate before allocating kernel pagetables in pagetable_init, so the kernel page-tables do not need to be discovered, and after all the early boot stuff is out of the way so everything can be neatly done in C code.
Zach _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
