From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: patches@linaro.org, stefano.stabellini@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH] xen/arm: Implement MPIDR per VCPU
Date: Thu, 13 Jun 2013 16:14:49 +0100 [thread overview]
Message-ID: <51B9E1E9.8040307@linaro.org> (raw)
In-Reply-To: <1371135553.6955.1.camel@zakaz.uk.xensource.com>
On 06/13/2013 03:59 PM, Ian Campbell wrote:
> On Fri, 2013-06-07 at 12:38 +0100, Julien Grall wrote:
>> Use different affinity for each VCPU and always expose an SMP systems to
>> the guest.
>
> What is the bad effect of not doing this for 4.3? Does it fix an
> observable bug?
I didn't notice a specific bug, Linux uses the MPDIR mainly for
optimizing scheduling. Unlike Xen, Linux doesn't use it to know which
CPU is booting so we can defer it.
--
Julien
prev parent reply other threads:[~2013-06-13 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:38 [PATCH] xen/arm: Implement MPIDR per VCPU Julien Grall
2013-06-12 15:11 ` Ian Campbell
2013-06-12 22:23 ` Julien Grall
2013-06-13 8:19 ` Ian Campbell
2013-06-13 9:46 ` Julien Grall
2013-06-13 14:59 ` Ian Campbell
2013-06-13 15:14 ` Julien Grall [this message]
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=51B9E1E9.8040307@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=patches@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=xen-devel@lists.xen.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).