On 08/06/15 11:52, Peter Maydell wrote: > On 8 June 2015 at 11:32, Igor Mammedov <imammedo@xxxxxxxxxx> wrote: >> On Thu, 4 Jun 2015 18:17:39 +0100 >> Peter Maydell <peter.maydell@xxxxxxxxxx> wrote: >>> On 4 June 2015 at 17:40, Shlomo Pongratz <shlomopongratz@xxxxxxxxx> wrote: >>> In order for it to work correctly we must use MPIDR values in >>> the device tree which match the MPIDR values the kernel has picked >>> for the vcpus, so ask KVM what those values are. > >> Could we set QEMU's generated mpidr in kernel instead of pulling it from kernel, >> like we do with APIC ID in x86 and fix kernel not to reset it its own value >> (i.e. untie mpidr from vcpuid)? >> >> Then later we could move setting mpidr from kvm_arch_init_vcpu() into >> board code which should be setting it, since it knows/defines what topology it has. > > This is a question better asked on the kvmarm list (which I have cc'd), > because that is where the kernel folks hang out... Care to provide some context? Why is this required? Thanks, M. -- Jazz is not dead. It just smells funny... _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
