From: Julien Grall <julien.grall@arm.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH 1/4] arm/percpu: Move {get, set}_processor_id() into smp.h
Date: Sat, 27 Jul 2019 13:41:51 +0100 [thread overview]
Message-ID: <3bb412c6-96d8-db09-e232-8114eb120b39@arm.com> (raw)
In-Reply-To: <f4ac56f4-d716-9454-c8ed-7115076597ff@citrix.com>
Hi Andrew,
On 7/26/19 11:37 PM, Andrew Cooper wrote:
> On 26/07/2019 23:30, Julien Grall wrote:
>> Hi Andrew,
>>
>> Thank you for looking into this.
>>
>> On 7/26/19 10:08 PM, Andrew Cooper wrote:
>>> For cleanup purposes, it is necessary for asm/percpu.h to not use
>>> DECLARE_PER_CPU() itself. asm/smp.h is arguably a better place for it to
>>> live anyway.
>> I have noticed that a lot of arch helpers called by common code
>> are defined in different headers. The most offenders are in mm.h
>> and page.h.
>
> Those are massive rats nests. At least we're slowly making progress on
> the outskirts.
>
> Lonterm, I'd like to get to a position where the only time you'd ever
> include an asm/ header is either from the common header itself, or for
> headers unique to the current architecture. I expect this to simplify
> things massively.
>
>>
>> Looking at x86, the two helpers are defined in current.h. So I
>> think it would make sense to define them at the same places. I
>> don't have a particular preference between smp.h and current.h,
>> just want some consistency :).
>>
>> FWIW, Xen build nicely when the helpers are moved in current.h:
>
> I did consider current.h, but couldn't decide and flipped a coin.
>
> I'm perfectly happy to put it here if that's what you'd prefer.
I would prefer consistency with x86 so, current.h :). Feel free to
re-use the diff I provided and add my acked-by.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-07-27 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 21:08 [Xen-devel] [PATCH 0/4] xen/percpu: Cleanup Andrew Cooper
2019-07-26 21:08 ` [Xen-devel] [PATCH 1/4] arm/percpu: Move {get, set}_processor_id() into smp.h Andrew Cooper
2019-07-26 22:30 ` Julien Grall
2019-07-26 22:37 ` Andrew Cooper
2019-07-27 12:41 ` Julien Grall [this message]
2019-07-26 21:08 ` [Xen-devel] [PATCH 2/4] xen/percpu: Drop unused xen/percpu.h includes Andrew Cooper
2019-07-29 8:55 ` Roger Pau Monné
2019-07-29 12:50 ` Jan Beulich
2019-07-26 21:08 ` [Xen-devel] [PATCH 3/4] xen/percpu: Drop unused asm/percpu.h includes Andrew Cooper
2019-07-26 22:32 ` Julien Grall
2019-07-29 8:56 ` Roger Pau Monné
2019-07-29 12:53 ` Jan Beulich
2019-07-26 21:08 ` [Xen-devel] [PATCH 4/4] xen/percpu: Make DECLARE_PER_CPU() and __DEFINE_PER_CPU() common Andrew Cooper
2019-07-26 22:34 ` Julien Grall
2019-07-29 8:58 ` Roger Pau Monné
2019-07-29 13:00 ` Jan Beulich
2019-07-29 13:23 ` Andrew Cooper
2019-07-29 13:54 ` Jan Beulich
2019-07-29 18:03 ` Andrew Cooper
2019-07-30 8:11 ` Jan Beulich
2019-07-31 4:58 ` Juergen Gross
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=3bb412c6-96d8-db09-e232-8114eb120b39@arm.com \
--to=julien.grall@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=sstabellini@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.