From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] ARM: keep __my_cpu_offset consistent with generic one
Date: Tue, 12 Mar 2013 10:25:05 -0700 [thread overview]
Message-ID: <20130312172505.GA25266@htj.dyndns.org> (raw)
In-Reply-To: <CACVXFVP4NeZBg5yZW8q+vhgs0m3knkkdvyjv_hc9BLrFPqEBJA@mail.gmail.com>
Hello,
On Tue, Mar 12, 2013 at 07:44:55PM +0800, Ming Lei wrote:
> On Tue, Mar 12, 2013 at 7:30 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >>
> >> Ingo and Peter, what is your opinion on the problem?
> >
> > Having discussed this with Ben Herrenschmidt, it seems that we do need
> > to have a more complex patch to sort this out - we need to setup our
> > private pointer inside setup_per_cpu_areas().
>
> Suppose so, seems the patch is still needed to make CPU0 see
> static variables in '.data..percpu' section correctly.
If my memory serves me right, x86 also has places where CPU0 accesses
its per-cpu data in .data.percpu. While those existed (not sure
they're still there but probably they're) mostly due to historical
reasons rather than by design, as long as the data is in consistent
state by and during percpu setup, nothing will break.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-03-12 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:35 [PATCH v1] ARM: keep __my_cpu_offset consistent with generic one Ming Lei
2013-03-12 2:32 ` Ming Lei
2013-03-12 10:56 ` Russell King - ARM Linux
2013-03-12 11:25 ` Ming Lei
2013-03-12 11:30 ` Russell King - ARM Linux
2013-03-12 11:44 ` Ming Lei
2013-03-12 17:25 ` Tejun Heo [this message]
2013-03-13 0:57 ` Ming Lei
2013-04-03 16:19 ` Russell King - ARM Linux
2013-04-04 6:31 ` Ming Lei
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=20130312172505.GA25266@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).