From: Andrew Jones <drjones@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
'Peter Crosthwaite' <crosthwaitepeter@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM CPU affinities
Date: Tue, 29 Sep 2015 08:15:30 +0200 [thread overview]
Message-ID: <20150929061530.GB4671@hawk.localdomain> (raw)
In-Reply-To: <020b01d0fa03$720720a0$561561e0$@samsung.com>
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
next prev parent reply other threads:[~2015-09-29 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 21:28 [Qemu-devel] ARM CPU affinities Peter Crosthwaite
2015-09-28 9:13 ` Peter Maydell
2015-09-28 11:49 ` Pavel Fedin
2015-09-28 15:12 ` Andrew Jones
2015-09-28 15:16 ` Pavel Fedin
2015-09-28 15:24 ` Andrew Jones
2015-09-28 15:36 ` Pavel Fedin
2015-09-29 6:15 ` Andrew Jones [this message]
2015-09-29 9:17 ` Peter Maydell
2015-09-28 16:56 ` Peter Crosthwaite
2015-09-28 17:04 ` Pavel Fedin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150929061530.GB4671@hawk.localdomain \
--to=drjones@redhat.com \
--cc=crosthwaitepeter@gmail.com \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).