From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>,
linux-kernel@vger.kernel.org, ltp-coverage@lists.sourceforge.net,
sam@ravnborg.org, rusty@rustcorp.com.au
Subject: Re: [PATCH 1/7] kernel: call constructors
Date: Tue, 20 May 2008 08:45:13 +0200 [thread overview]
Message-ID: <48327379.7030506@de.ibm.com> (raw)
In-Reply-To: <20080519150640.c61dca49.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 19 May 2008 10:43:14 +0200
> Peter Oberparleiter <peter.oberparleiter@de.ibm.com> wrote:
>
>> From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
>>
>> Call constructors during kernel init and module load. Required by the
>> gcov profiling infrastructure: gcc's profiling code uses constructors
>> to register profiling data structures.
>>
>
> What happens with architectures which do not use
> include/asm-generic/vmlinux.lds.h? A quicky grep points at
In that case, no constructors would be called and as a result the gcov
debugfs directory would be empty. This should be easily fixable as the
case arises though. I've re-checked arch/*/vmlinux* and all of those
linker scripts seem to include asm-generic/vmlinux.lds.h at most via
one indirection.
> arch/m68k/kernel/vmlinux.lds.S
Includes asm-generic/vmlinux.lds.h either via vmlinux-sun3.lds or
vmlinux-std.lds.
> arch/sh/kernel/vmlinux.lds.S
Includes asm-generic/vmlinux.lds.h either via vmlinux_32.lds.S or
vmlinux_64.lds.S.
> arch/um/kernel/vmlinux.lds.S
Includes asm-generic/vmlinux.lds.h either via uml.lds.S or dyn.lds.S.
Regards,
Peter
prev parent reply other threads:[~2008-05-20 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:43 [PATCH 1/7] kernel: call constructors Peter Oberparleiter
2008-05-19 22:06 ` Andrew Morton
2008-05-20 6:45 ` Peter Oberparleiter [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=48327379.7030506@de.ibm.com \
--to=peter.oberparleiter@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=rusty@rustcorp.com.au \
--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 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.