From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH] xen: arm: ignore CPUs which are not marked available in the DT
Date: Wed, 23 Jul 2014 19:36:50 +0100 [thread overview]
Message-ID: <1406140610.29480.5.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <53CFEDB3.4000702@linaro.org>
On Wed, 2014-07-23 at 18:15 +0100, Julien Grall wrote:
> Hi Ian,
>
> On 07/23/2014 05:45 PM, Ian Campbell wrote:
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > ---
> > xen/arch/arm/smpboot.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/xen/arch/arm/smpboot.c b/xen/arch/arm/smpboot.c
> > index cf149da..4b0a738 100644
> > --- a/xen/arch/arm/smpboot.c
> > +++ b/xen/arch/arm/smpboot.c
> > @@ -134,6 +134,9 @@ void __init smp_init_cpus(void)
> > if ( !dt_device_type_is_equal(cpu, "cpu") )
> > continue;
> >
> > + if ( !dt_device_is_available(cpu) )
> > + continue;
> > +
>
> I can't find a such things on the Linux device tree bindings.
status is a generic property which is common to all nodes, it comes from
ePAPR.
> Do you
> have a use case where CPU are marked disabled?
I use it locally when booting with models -- it allows me to turn off
cpus in the base .dts file using a wrapper instead of having to edit the
original.
Ian.
next prev parent reply other threads:[~2014-07-23 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 16:45 [PATCH] xen: arm: ignore CPUs which are not marked available in the DT Ian Campbell
2014-07-23 17:15 ` Julien Grall
2014-07-23 18:36 ` Ian Campbell [this message]
2014-07-24 10:36 ` Julien Grall
2014-07-24 10:40 ` Ian Campbell
2014-07-24 10:44 ` Julien Grall
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=1406140610.29480.5.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--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).