qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
	Pavel Fedin <p.fedin@samsung.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM CPU affinities
Date: Mon, 28 Sep 2015 17:12:22 +0200	[thread overview]
Message-ID: <20150928151222.GB3841@hawk.localdomain> (raw)
In-Reply-To: <CAFEAcA_XGuyzR6Bd957y+WuVsFtAR72qpwo58Gj6W3+uz77eVQ@mail.gmail.com>

On Mon, Sep 28, 2015 at 10:13:15AM +0100, Peter Maydell wrote:
> On 27 September 2015 at 22:28, Peter Crosthwaite
> <crosthwaitepeter@gmail.com> wrote:
> > Hi Peter,
> >
> > I am looking at this:
> >
> > static void arm_cpu_initfn(Object *obj)
> > {
> >     ...
> >     Aff1 = cs->cpu_index / ARM_CPUS_PER_CLUSTER;
> >     Aff0 = cs->cpu_index % ARM_CPUS_PER_CLUSTER;
> >     cpu->mp_affinity = (Aff1 << ARM_AFF1_SHIFT) | Aff0;
> >
> >
> > Should we push this up to the machine model? I am trying to fix a
> > machine where Aff1 of the one and only cluster is non-zero. The kernel
> > SMP support barfs when Aff1 is mismatched to whats in the DTB (CPU reg
> > property).
> >
> > I think this modulo 8 starting from 0:0 policy might be specific to mach-virt?
> 
> Yeah, it should be a CPU property if you need it to be something
> different. I think we just left it as a hardcoded thing until
> somebody needed it to be different.
> 
> NB that as the comment says KVM currently imposes its own numbering
> anyway -- if you care about that you need to get the kernel to
> support having userspace tell it about affinity numbering.

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?

Thanks,
drew

  parent reply	other threads:[~2015-09-28 15:12 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 [this message]
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
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=20150928151222.GB3841@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).