On Mon, Sep 28, 2015 at 06:36:29PM +0300, Pavel Fedin wrote: > Hello! > > > I think we'll need to cache mpidr in the vcpu data in order to properly > > reset it. > > We already have it in our data. I took a quick look at that, but kernel > needs patching. IIRC reset
Right. I was referring to the kernel's vcpu data (struct kvm_vcpu). > for secondary vCPUs happens inside kernel's PSCI code, before primary tells > it to start up. You > cannot separate these two events. > In a short: you can use KVM_SET_ONE_REG for the MPIDR, and the value will go > into kernel, but as > soon as you call KVM_VCPU_RUN for the secondary, it gets reset. My current thinking is that we'll set MPIDR with KVM_SET_ONE_REG, which will also set the cached value in struct kvm_vcpu. Reset will then use that value. Thanks, drew
