* Avi Kivity <avi@xxxxxxxxxx> [2009-04-28 05:53]: > Michael S. Tsirkin wrote: > >>Or maybe, add a s/CONFIG_KVM_TRACE/CONFIG_KMOD_KVM_TRACE/ to make the > >>two options independent. > >> > > > >You decide. > > Well, I think it's less confusing. > > >I also wonder what happens if one tries to build on > >a machine with kvm built into kernel. Ideally one would get > >a clear error message. > > > > kvm-kmod is really designed for those running on pre-kvm distro kernels, > and for those testing newer kvm versions on distro kernels. If you can > compile your own kernel, download kvm.git and run that. So no way of having kvm-kmod sync in kvm.git bits and still build against the current running kernel? I wanted to test out 2.6.29-maint kernel modules and in kvm-userspace/kernel, I could checkout maint/2.6.29 in kvm.git and then make LINUX= sync. I couldn't quite figure out how to do that with kvm-kmod since when I do a ./configure --kerneldir -- it's building modules *for* whatever kernel is at kerneldir rather than just syncing in the kvm bits from that kerneldir and then building modules against the running kernel. The reason I'm digging is that I'm seeing 64-bit migration failing on maint/2.6.29 kvm modules, but not on upstream kvm kernel bits and I wanted to bisect to find where 64-bit migration is fixed so I can suggest what to pull into maint/2.6.29. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
