From: Steven Rostedt <rostedt@goodmis.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 05/05] percpu i386 linker script update
Date: Fri, 14 Apr 2006 17:31:47 -0400 [thread overview]
Message-ID: <1145050307.17627.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20060414212355.GB12482@mars.ravnborg.org>
On Fri, 2006-04-14 at 23:23 +0200, Sam Ravnborg wrote:
> On Fri, Apr 14, 2006 at 05:19:33PM -0400, Steven Rostedt wrote:
> > Add .data.percpu_offset section into arch/i386
> >
> > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> >
> > Index: linux-2.6.17-rc1/arch/i386/kernel/vmlinux.lds.S
> > ===================================================================
> > --- linux-2.6.17-rc1.orig/arch/i386/kernel/vmlinux.lds.S 2006-04-14 15:43:49.000000000 -0400
> > +++ linux-2.6.17-rc1/arch/i386/kernel/vmlinux.lds.S 2006-04-14 15:58:08.000000000 -0400
> > @@ -62,6 +62,9 @@ SECTIONS
> > /* rarely changed data like cpu maps */
> > . = ALIGN(32);
> > .data.read_mostly : AT(ADDR(.data.read_mostly) - LOAD_OFFSET) { *(.data.read_mostly) }
> > + __per_cpu_offset_start = .;
> > + .data.percpu_offset : AT(ADDR(.data.percpu_offset) - LOAD_OFFSET) { *(.data.percpu_offset) }
> > + __per_cpu_offset_end = .;
> > _edata = .; /* End of data section */
> >
> > . = ALIGN(THREAD_SIZE); /* init_task */
>
> Can we please have this definition in:
> include/asm-generic/vmlinux.lds.h
>
> At least it looks to make sense for other arch's than just i386.
>
> Something like
> #define PERCPU_OFFSET \
> ...
Sounds good, thanks!
-- Steve
prev parent reply other threads:[~2006-04-14 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 21:19 Steven Rostedt
2006-04-14 21:23 ` Sam Ravnborg
2006-04-14 21:31 ` Steven Rostedt [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=1145050307.17627.1.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®