From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "George G. Davis" <gdavis@mvista.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Vincent Sanders <vincent.sanders@collabora.co.uk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Vincent Sanders <vince@collabora.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] Allow constructor name selection by architecture.
Date: Thu, 18 Apr 2013 13:39:31 +0100 [thread overview]
Message-ID: <20130418123931.GR14496@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAE1uF8dCy3m3TO4xa6Cc3i-CM3QYUFADZH_6o+hgy6MSPEWnyQ@mail.gmail.com>
Looks to me like this has died again. Unless Sam responds shortly,
I'm going to ask for this to be put into the patch system and I'll
just apply it for 3.10 and be done with it.
On Mon, Apr 01, 2013 at 06:21:51PM -0400, George G. Davis wrote:
> On Mon, Apr 1, 2013 at 5:58 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
> > On Mon, Apr 01, 2013 at 05:47:38PM -0400, George G. Davis wrote:
> >> On Jun 6, 2012, at 6:12 AM, Russell King - ARM Linux wrote:
> >> > On Tue, May 29, 2012 at 10:06:14AM +0100, Russell King - ARM Linux wrote:
> >> >> On Mon, May 28, 2012 at 10:30:05PM +0200, Sam Ravnborg wrote:
> >> >>> On Mon, May 28, 2012 at 07:33:37PM +0100, Vincent Sanders wrote:
> >> >>>> From: Vincent Sanders <vince@collabora.co.uk>
> >> >>>>
> >> >>>> The constructor symbol name is different between platforms. Allow this
> >> >>>> to be selected by configuration and set suitable default values.
> >> >>>>
> >> >>>> Signed-off-by: Vincent Sanders <vincent.sanders@collabora.co.uk>
> >> >>>> ---
> >> >>>> include/asm-generic/vmlinux.lds.h | 6 +++---
> >> >>>> init/Kconfig | 6 ++++++
> >> >>>> kernel/module.c | 2 +-
> >> >>>> 3 files changed, 10 insertions(+), 4 deletions(-)
> >> >>>>
> >> >>>> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> >> >>>> index 8aeadf6..fd34808 100644
> >> >>>> --- a/include/asm-generic/vmlinux.lds.h
> >> >>>> +++ b/include/asm-generic/vmlinux.lds.h
> >> >>>> @@ -471,9 +471,9 @@
> >> >>>> }
> >> >>>>
> >> >>>> #ifdef CONFIG_CONSTRUCTORS
> >> >>>> -#define KERNEL_CTORS() . = ALIGN(8); \
> >> >>>> - VMLINUX_SYMBOL(__ctors_start) = .; \
> >> >>>> - *(.ctors) \
> >> >>>> +#define KERNEL_CTORS() . = ALIGN(8); \
> >> >>>> + VMLINUX_SYMBOL(__ctors_start) = .; \
> >> >>>> + *(CONFIG_CONSTRUCTORS_NAME) \
> >> >>>> VMLINUX_SYMBOL(__ctors_end) = .;
> >> >>>
> >> >>> What is wrong with adding both "standard" names for ctors uncnditionally?
> >> >>> Like this:
> >> >>>> *(.ctors) \
> >> >>>> + *(.init_array) \
> >> >>
> >> >> That doesn't get rid of CONFIG_CONSTRUCTORS_NAME, because it's needed
> >> >> in the module code. Do you have a suggestion to solve that as well?
> >> >
> >> > Ping.
> >>
> >> Pinging this back to life. I'd like to see GCOV for ARM eABI finally make it upstream.
> >> So, any objections to this? Should it be resubmitted?
> >
> > Why is CONFIG_CONSTRUCTORS_NAME needed in module code?
>
> Because ARM eABI uses the .init_array section for C++ constructors,
> rather than .ctors.
> So the patch defined CONFIG_CONSTRUCTORS_NAME to set the correct section name
> for ARM eABI while leaving non-ARM-eABI as before, .ctors. Here are the changes
> from the patch for reference:
>
> diff --git a/init/Kconfig b/init/Kconfig
> index 6cfd71d..52181a1 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -20,6 +20,12 @@ config CONSTRUCTORS
> bool
> depends on !UML
>
> +config CONSTRUCTORS_NAME
> + string
> + depends on CONSTRUCTORS
> + default ".init_array" if ARM && AEABI
> + default ".ctors"
> +
> config HAVE_IRQ_WORK
> bool
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 78ac6ec..e5fad5e 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -2600,7 +2600,7 @@ static void find_module_sections(struct module
> *mod, struct load_info *info)
> mod->unused_gpl_crcs = section_addr(info, "__kcrctab_unused_gpl");
> #endif
> #ifdef CONFIG_CONSTRUCTORS
> - mod->ctors = section_objs(info, ".ctors",
> + mod->ctors = section_objs(info, CONFIG_CONSTRUCTORS_NAME,
> sizeof(*mod->ctors), &mod->num_ctors);
> #endif
>
> W/o the above, GCOV does not work on ARM eABI for kernel modules.
> Meanwhile, it still works as before for non-ARM-eABI kernel modules.
>
> Thanks!
>
> --
> Regards,
> George
next prev parent reply other threads:[~2013-04-18 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 18:33 Add gcov support to ARM Vincent Sanders
2012-05-28 18:33 ` [PATCH 1/2] Allow constructor name selection by architecture Vincent Sanders
2012-05-28 20:30 ` Sam Ravnborg
2012-05-29 9:06 ` Russell King - ARM Linux
2012-06-06 10:12 ` Russell King - ARM Linux
2013-04-01 21:47 ` George G. Davis
2013-04-01 21:58 ` Sam Ravnborg
2013-04-01 22:21 ` George G. Davis
2013-04-18 12:39 ` Russell King - ARM Linux [this message]
2013-04-22 8:56 ` Sam Ravnborg
2012-05-29 9:21 ` Vincent Sanders
2012-05-28 18:33 ` [PATCH 2/2] Enable gcov support on the ARM architecture Vincent Sanders
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=20130418123931.GR14496@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gdavis@mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=vince@collabora.co.uk \
--cc=vincent.sanders@collabora.co.uk \
/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®