On Wed, Jan 09, 2013 at 11:16:42AM +0000, Pekka Enberg wrote: > Hi Will, Hello, > On Mon, Jan 7, 2013 at 8:43 PM, Will Deacon <will.deacon@xxxxxxx> wrote: > > These two patches add support for ARMv8 processors running an AArch64 instance > > of kvm to kvmtool. Both AArch32 and AArch64 guests are supported and, in the > > case of the latter, the guest page size may be either 64k or 4k. > > > > This depends on the ARM updates series I just posted: > > > > https://lists.cs.columbia.edu/pipermail/kvmarm/2013-January/004505.html > > > > Feedback welcome, > > So will ARMv7 continue to work after this patch even without the ARM > updates? If so, I'm happy to merge the patch before the updates hit > v3.9. I think we're getting our wires crossed a bit here, so I'll try to explain my madness: - Mainline ARM kernels cannot be booted by kvmtool yet, you currently have to use my virt/mach branch from git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git I hope to upstream this for 3.9 (it has gone through the necessary review on the ARM kernel list). - As part of the review mentioned above, some kvmtool changes were required to support SMP with the latest virt/mach. You just merged these in my ARM updates series. - The ARMv8 kvmtool code builds on top of the series you just merged and won't apply without it. Applying it won't have any adverse effects on ARMv7 (AArch32). In fact, the two series sit together on my kvmtool/arm branch from git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git but I posted them separately to avoid holding up the ARM updates. Does that answer you question or have I made things worse?! Cheers, Will -- 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
