On Tue, Jan 22, 2008 at 01:02:07PM +0100, Ingo Molnar wrote: > > * Eduardo Habkost <ehabkost@xxxxxxxxxx> wrote: > > > This series contain fixes to make the paravirt_ops code compile and > > boot on x86_64. > > > > This is a follow-up for the previous series from Glauber. > > thanks Eduardo, i've applied your fixes. > > could you perhaps send the missing bits that add the missing 64-bit > Kconfig entries? Even if the 64-bit side is not functional yet as a real > guest, it would help us find the build bugs and any runtime regressions > PARAVIRT might cause on the native 64-bit side of the kernel. > > Or is it now just a matter of removing all the depends-on X86_32 bits in > arch/x86/Kconfig? Removing the depends won't be enough because CONFIG_PARAVIRT won't be selected unless one of Xen, VMI, or lguest is selected. (PARAVIRT is not visible on menuconfig, only PARAVIRT_GUEST, that doesn't enable any code). When hacking, I remove the 32-bit depends and add "select PARAVIRT" to "menuconfig PARAVIRT_GUEST". I think neither of the three guest implementations are ready for 64-bit yet. I am working on Xen and it is far from being ready for inclusion. I don't know about VMI and lguest. If this is desirable for broader testing, we can make config PARAVIRT visible and selectable on menuconfig, even when there is no guest implementation being enabled. Should I do it? Maybe should this force-paravirt mode be a kernel debugging option? -- Eduardo _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
