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: Mon, 28 Sep 2015 17:24:43 +0200 [thread overview]
Message-ID: <20150928152443.GC3841@hawk.localdomain> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAALZbhr4r3r1Hrv6/MJGlVlrCgAAAEAAAAPvEDuxV32pOk41SdtW7gvUBAAAAAA==@samsung.com>
On Mon, Sep 28, 2015 at 06:16:26PM +0300, Pavel Fedin wrote:
> Hello!
>
> > I've been thinking about picking this work up. Let me confirm first that
> > Pavel hasn't already, because, iirc, he was the last to look into it.
> > Pavel?
>
> I am here. Yes, i did not do anything else with this. The problem is in the kernel; every time vCPU
> is reset, it resets its MPIDR value to something that it wants it to be. IIRC the hardcoded
> assignment is 16 CPUs per cluster starting from 0:0.
I think we'll need to cache mpidr in the vcpu data in order to properly
reset it.
>
> I have some strange problem with delivering mails, my emails do not seem to make it to the list.
> Please reply me privately if you got this.
Got your mail, replying not only to you, but also the list though, as I'll
use the opportunity to confirm that I'll go ahead and pick up this work.
Thanks,
drew
next prev parent reply other threads:[~2015-09-28 15:24 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 [this message]
2015-09-28 15:36 ` Pavel Fedin
2015-09-29 6:15 ` Andrew Jones
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=20150928152443.GC3841@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).