From: Julien Grall <julien.grall@linaro.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
ian.campbell@citrix.com, tim@xen.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
stefano.stabellini@citrix.com, Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 1/6] xen: Add convenient macro boot_cpu
Date: Tue, 06 May 2014 16:54:04 +0100 [thread overview]
Message-ID: <5369059C.7060506@linaro.org> (raw)
In-Reply-To: <5363C07F.8040603@citrix.com>
Hi Andrew,
On 05/02/2014 04:57 PM, Andrew Cooper wrote:
> On 02/05/14 16:52, Julien Grall wrote:
>> The macro boot_cpu will be used to get CPU variable from the boot CPU.
>>
>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>> Suggested-by: Ian Campbell <ian.campbell@citrix.com>
>> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
>> Cc: Jan Beulich <jbeulich@suse.com>
>> Cc: Keir Fraser <keir@xen.org>
>> ---
>> xen/include/xen/percpu.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/xen/include/xen/percpu.h b/xen/include/xen/percpu.h
>> index abe0b11..0e848bf 100644
>> --- a/xen/include/xen/percpu.h
>> +++ b/xen/include/xen/percpu.h
>> @@ -16,6 +16,9 @@
>> /* Preferred on Xen. Also see arch-defined per_cpu(). */
>> #define this_cpu(var) __get_cpu_var(var)
>>
>> +/* Access variable on boot CPU */
>> +#define boot_cpu(var) per_cpu(var, 0)
>> +
>
> What is this actually used for?
I use it to retrieve PPIs (per-processor interrupt) type and initialize
PPIs for the new CPUs.
> In x86 with arbitrary cpu hotplug, we are trying to move away from the
> false assumption than cpu0 is the boot cpu. Actual boot data is stored
> sideways as boot_$FOO variables, and not accessed with the per-cpu
> mechanism.
My solution won't work for hotplug. As it's not supported for ARM right
now, I think we can live with it.
I can either drop the macro or make ARM specific for now.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-05-06 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 15:52 [PATCH v5 0/6] xen/arm: Interrupt management reworking Julien Grall
2014-05-02 15:52 ` [PATCH v5 1/6] xen: Add convenient macro boot_cpu Julien Grall
2014-05-02 15:57 ` Andrew Cooper
2014-05-06 15:54 ` Julien Grall [this message]
2014-05-08 9:57 ` Ian Campbell
2014-05-12 12:36 ` Julien Grall
2014-05-08 9:55 ` Ian Campbell
2014-05-08 10:00 ` Jan Beulich
2014-05-08 10:19 ` Ian Campbell
2014-05-05 7:59 ` Jan Beulich
2014-05-06 15:58 ` Julien Grall
2014-05-06 16:04 ` Jan Beulich
2014-05-06 16:09 ` Andrew Cooper
2014-05-02 15:52 ` [PATCH v5 2/6] xen/arm: IRQ: Store IRQ type in arch_irq_desc Julien Grall
2014-05-08 10:03 ` Ian Campbell
2014-05-12 12:34 ` Julien Grall
2014-05-02 15:52 ` [PATCH v5 3/6] xen/arm: IRQ: Replace {request, setup}_dt_irq by {request, setup}_irq Julien Grall
2014-05-02 15:52 ` [PATCH v5 4/6] xen: IRQ: Add dev_id parameter to release_irq Julien Grall
2014-05-02 15:52 ` [PATCH v5 5/6] xen/arm: IRQ: extend {request, setup}_irq to take an irqflags in parameter Julien Grall
2014-05-02 15:52 ` [PATCH v5 6/6] xen/arm: IRQ: Handle multiple action per IRQ Julien Grall
2014-05-08 10:04 ` Ian Campbell
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=5369059C.7060506@linaro.org \
--to=julien.grall@linaro.org \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).