On Thu, Aug 08, 2013 at 07:20:41PM +0100, Peter Maydell wrote: > >> For ARM you can't get at feature info of the host from userspace > >> (unless you want to get into parsing /proc/cpuinfo), so my current > >> idea is to have KVM_ARM_VCPU_INIT support a target-cpu-type > >> which means "whatever host CPU is". Then when we've created the > >> vcpu we can populate QEMU's idea of what the CPU features are > >> by using the existing ioctls for reading the cp15 registers of > >> the vcpu. > > > > Sounds sane to me iff those cp15 registers all work with KVM and don't > > need any additional KVM/QEMU/device code. > > Yes; KVM won't tell us about CP15 registers unless they > are exposed to the guest VM (that is, we're querying the So why not implement something similar to x86 cpuid thing. Have separate ioctls to query what CP15 registers KVM can support and what is exposed to a guest? > VCPU, not the host CPU). More generally, the cp15 "tuple > list" code I landed a couple of months back makes the kernel > the authoritative source for which cp15 registers exist and > what their values are -- in -enable-kvm mode QEMU no longer > cares about them (its own list of which registers exist for > which CPU is used only for TCG). > -- Gleb. -- 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
