On Fri, 2015-05-08 at 10:19 +0200, Thomas Huth wrote: > On Fri, 8 May 2015 09:07:18 +1000 > Paul Mackerras <paulus@xxxxxxxxx> wrote: > > > On Thu, May 07, 2015 at 05:49:39PM +0200, Thomas Huth wrote: > > > Both functions are doing the same thing - looking up the struct > > > kvm_vcpu pointer for a given vCPU ID. > > > > No, kvm_get_vcpu(n) returns the n'th vcpu created, which is often > > but not necessarily the same as the vcpu with id n. In fact, due to > > the way we do threading in HV KVM, it's quite common for userspace to > > create vcpus with ids 0, 8, 16, ..., which means that the n'th vcpu > > created does not have id n (except of course for vcpu 0). A patch adding a comment explaining that subtlety would be welcome from anyone who sent it :) cheers -- 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
