From: Russell King <rmk@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
fenghua.yu@intel.com, ak@suse.de, clameter@sgi.com,
linux-arch@vger.kernel.org, rusty@rustcorp.com.au,
suresh.b.siddha@intel.com, tony.luck@intel.com
Subject: Re: [patch 055/209] define new percpu interface for shared data
Date: Thu, 19 Jul 2007 21:08:37 +0100 [thread overview]
Message-ID: <20070719200837.GA32040@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070719200253.GB15186@uranus.ravnborg.org>
On Thu, Jul 19, 2007 at 10:02:53PM +0200, Sam Ravnborg wrote:
> On Thu, Jul 19, 2007 at 01:48:12AM -0700, akpm@linux-foundation.org wrote:
> >
> > Moves the remotely accessed per cpu data (which is currently marked
> > as ____cacheline_aligned_in_smp) into a different section, where all the data
> > elements are cacheline aligned. And as such, this differentiates the local
> > only data and remotely accessed data cleanly.
> >
> > --- a/arch/arm/kernel/vmlinux.lds.S~define-new-percpu-interface-for-shared-data-version-4
> > +++ a/arch/arm/kernel/vmlinux.lds.S
> > @@ -66,6 +66,7 @@ SECTIONS
> > . = ALIGN(4096);
> > __per_cpu_start = .;
> > *(.data.percpu)
> > + *(.data.percpu.shared_aligned)
> > __per_cpu_end = .;
> > #ifndef CONFIG_XIP_KERNEL
> > __init_begin = _stext;
>
> Why is PERCPU not suitable for arm?
You can't put an output section inside an output section.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-07-19 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 8:48 [patch 055/209] define new percpu interface for shared data akpm
2007-07-19 20:02 ` Sam Ravnborg
2007-07-19 20:08 ` Russell King [this message]
2007-07-19 20:34 ` Yu, Fenghua
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=20070719200837.GA32040@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=fenghua.yu@intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=suresh.b.siddha@intel.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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.