From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, andi@firstfloor.org,
ying.huang@intel.com, W.Li@Sun.COM, michaele@au1.ibm.com,
mingo@elte.hu, heicars2@linux.vnet.ibm.com,
mschwid2@linux.vnet.ibm.com, rusty@rustcorp.com.au,
xiyou.wangcong@gmail.com, sam@ravnborg.org, jdike@addtoit.com
Subject: Re: [PATCH 1/4] kernel: constructor support
Date: Tue, 2 Jun 2009 14:32:02 -0700 [thread overview]
Message-ID: <20090602143202.6cfcc4ce.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090602114400.740271397@linux.vnet.ibm.com>
On Tue, 02 Jun 2009 13:44:00 +0200
Peter Oberparleiter <oberpar@linux.vnet.ibm.com> wrote:
> From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
>
> Call constructors (gcc-generated initcall-like functions) during
> kernel start and module load. Constructors are e.g. used for gcov data
> initialization.
>
> Disable constructor support for usermode Linux to prevent conflicts
> with host glibc.
>
> Signed-off-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
> Acked-by: Rusty Russell <rusty@rustcorp.com.au>
> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Jeff Dike <jdike@addtoit.com>
>
> ...
>
> --- linux-2.6.30-rc7.orig/include/asm-generic/vmlinux.lds.h 2009-06-02 10:34:37.000000000 +0200
> +++ linux-2.6.30-rc7/include/asm-generic/vmlinux.lds.h 2009-06-02 10:35:20.000000000 +0200
Sam's tree has mucked with this file in linux-next.
> @@ -332,6 +332,14 @@
> /* Section used for early init (in .S files) */
> #define HEAD_TEXT *(HEAD_TEXT_SECTION)
>
> +#ifdef CONFIG_CONSTRUCTORS
> +#define KERNEL_CTORS() VMLINUX_SYMBOL(__ctors_start) = .; \
> + *(.ctors) \
> + VMLINUX_SYMBOL(__ctors_end) = .;
> +#else
> +#define KERNEL_CTORS()
> +#endif
> +
> /* init and exit section handling */
> #define INIT_DATA \
> *(.init.data) \
> @@ -340,7 +348,8 @@
> CPU_DISCARD(init.data) \
> CPU_DISCARD(init.rodata) \
> MEM_DISCARD(init.data) \
> - MEM_DISCARD(init.rodata)
> + MEM_DISCARD(init.rodata) \
> + KERNEL_CTORS()
>
What we now have here is
#define INIT_DATA \
*(.init.data) \
DEV_DISCARD(init.data) \
CPU_DISCARD(init.data) \
MEM_DISCARD(init.data) \
*(.init.rodata) \
DEV_DISCARD(init.rodata) \
CPU_DISCARD(init.rodata) \
MEM_DISCARD(init.rodata)
and I don't think that you wanted KERNEL_DTORS() inside the .rodata
section, so I did this:
#define INIT_DATA \
*(.init.data) \
DEV_DISCARD(init.data) \
CPU_DISCARD(init.data) \
MEM_DISCARD(init.data) \
KERNEL_CTORS() \
*(.init.rodata) \
DEV_DISCARD(init.rodata) \
CPU_DISCARD(init.rodata) \
MEM_DISCARD(init.rodata)
Please check that?
next prev parent reply other threads:[~2009-06-02 21:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 11:43 [PATCH 0/4] gcov kernel support Peter Oberparleiter
2009-06-02 11:44 ` [PATCH 1/4] kernel: constructor support Peter Oberparleiter
2009-06-02 21:32 ` Andrew Morton [this message]
2009-06-03 11:55 ` Peter Oberparleiter
2009-06-02 11:44 ` [PATCH 2/4] seq_file: add function to write binary data Peter Oberparleiter
2009-06-02 11:44 ` [PATCH 3/4] gcov: add gcov profiling infrastructure Peter Oberparleiter
2009-06-02 22:03 ` Andrew Morton
2009-06-03 2:34 ` Michael Ellerman
2009-06-03 11:57 ` Peter Oberparleiter
2009-06-03 15:26 ` Peter Oberparleiter
2009-06-03 16:01 ` Michael Ellerman
2009-06-03 21:39 ` Andrew Morton
2009-06-04 8:26 ` Peter Oberparleiter
2009-06-04 8:40 ` Andrew Morton
2009-06-05 13:05 ` Peter Oberparleiter
2009-06-04 9:08 ` Amerigo Wang
2009-06-05 9:23 ` Peter Oberparleiter
2009-06-05 9:34 ` Andrew Morton
2009-06-05 10:12 ` Peter Oberparleiter
2009-06-06 8:30 ` Michael Ellerman
2009-06-08 8:24 ` Peter Oberparleiter
2009-06-05 9:55 ` Amerigo Wang
2009-06-02 11:44 ` [PATCH 4/4] gcov: enable GCOV_PROFILE_ALL for x86_64 Peter Oberparleiter
-- strict thread matches above, loose matches on Subject: below --
2009-05-19 14:24 [PATCH 0/4] gcov kernel support Peter Oberparleiter
2009-05-19 14:24 ` [PATCH 1/4] kernel: constructor support Peter Oberparleiter
2009-05-12 15:38 [PATCH 0/4] gcov kernel support Peter Oberparleiter
2009-05-12 15:38 ` [PATCH 1/4] kernel: constructor support Peter Oberparleiter
2009-05-08 15:44 [PATCH 0/4] gcov kernel support Peter Oberparleiter
2009-05-08 15:44 ` [PATCH 1/4] kernel: constructor support Peter Oberparleiter
2009-05-09 5:03 ` Américo Wang
2009-05-11 8:43 ` Peter Oberparleiter
2009-05-11 18:54 ` Sam Ravnborg
2009-05-12 13:12 ` Peter Oberparleiter
2009-05-07 12:45 [PATCH 0/4] gcov kernel support Peter Oberparleiter
2009-05-07 12:45 ` [PATCH 1/4] kernel: constructor support Peter Oberparleiter
2009-05-07 12:51 ` Ingo Molnar
2009-05-07 13:33 ` Peter Oberparleiter
2009-05-07 12:53 ` Ingo Molnar
2009-05-07 13:38 ` Peter Oberparleiter
2009-05-07 13:48 ` Ingo Molnar
2009-05-08 11:23 ` Peter Oberparleiter
2009-02-26 13:51 Peter Oberparleiter
2009-02-03 12:46 Peter Oberparleiter
2009-02-04 2:54 ` Rusty Russell
2009-02-04 15:05 ` Peter Oberparleiter
2009-02-04 23:23 ` Rusty Russell
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=20090602143202.6cfcc4ce.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=W.Li@Sun.COM \
--cc=andi@firstfloor.org \
--cc=heicars2@linux.vnet.ibm.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaele@au1.ibm.com \
--cc=mingo@elte.hu \
--cc=mschwid2@linux.vnet.ibm.com \
--cc=oberpar@linux.vnet.ibm.com \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.org \
--cc=xiyou.wangcong@gmail.com \
--cc=ying.huang@intel.com \
/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
Powered by JetHome