On Wed, Mar 08, 2017 at 03:27:28PM +0100, Peter Maydell wrote: > On 8 March 2017 at 14:19, Christoffer Dall <christoffer.dall@xxxxxxxxxx> wrote: > > Isn't this all super racy? What prevents two VCPUs from getting the > > same MPIDR at the same time? > > From a userspace API point of view, I was expecting this to be > "just don't do that then" territory, ie it's userspace's job > to set the MPIDRs to something that makes sense. Does KVM > actually care internally what the MPIDR presented to the guest is? > (In theory I don't see why you shouldn't be able to present > the guest with a bit of bogus hardware that claims the same > MPIDR for all cores.) > I think it's important that we maintain a strict mapping between an MPIDR and a VCPU at any given time, because otherwise, we'll have problems knowing which redestributor belongs to which VCPU and making other qualified decisions in the KVM/ARM implementation. Thanks, -Christoffer _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
