xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
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: Thu, 24 Jul 2014 11:44:47 +0100	[thread overview]
Message-ID: <53D0E39F.9010802@linaro.org> (raw)
In-Reply-To: <1406198454.555.1.camel@kazak.uk.xensource.com>



On 24/07/14 11:40, Ian Campbell wrote:
> On Thu, 2014-07-24 at 11:36 +0100, Julien Grall wrote:
>> Hi Ian,
>>
>> On 23/07/14 19:36, Ian Campbell wrote:
>>> On Wed, 2014-07-23 at 18:15 +0100, Julien Grall wrote:
>>>> 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.
>>
>> I read the ePAPR and the property status on CPU node. AFAIU, the
>> property doesn't have this meaning for a such node.
>>
>> This property means the CPU is in quiescent state and property to bring
>> up the CPU is provides in the device tree node.
>>
>> Section 5.5.2.2:
>>
>> Before starting a client program on the boot cpu, the boot program shall
>> set certain properties in the
>> device tree passed to the client as follows:
>> • Each secondary CPU’s cpu node shall have a status property with a
>> value of “disabled”.
>
> Oh well, it was only a convenience for me anyway.
> Ian

Could we add a property xen,status for debugging (i.e when Xen is 
compiled with debug=y)? So we don't collapse with the actual property if 
someone decide to implement it in the bootloader.

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2014-07-24 10:44 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
2014-07-24 10:36     ` Julien Grall
2014-07-24 10:40       ` Ian Campbell
2014-07-24 10:44         ` 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=53D0E39F.9010802@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --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).