linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: linux-kernel@vger.kernel.org, jstancek@redhat.com,
	keescook@chromium.org, rusty@rustcorp.com.au,
	linux-arch@vger.kernel.org, arnd@arndb.de, mgahagan@redhat.com,
	agospoda@redhat.com
Subject: Re: [RFC PATCH 4/4] kernel: add support for init_array constructors
Date: Fri, 23 Aug 2013 17:13:31 +0200	[thread overview]
Message-ID: <52177C1B.60107@linux.vnet.ibm.com> (raw)
In-Reply-To: <1377247176-13537-5-git-send-email-fhrbata@redhat.com>

On 23.08.2013 10:39, Frantisek Hrbata wrote:
> This adds the .init_array section as yet another section with constructors. This
> is needed because gcc is adding __gcov_init calls to .init_array.
> 
> Signed-off-by: Frantisek Hrbata <fhrbata@redhat.com>
> ---
>  include/asm-generic/vmlinux.lds.h | 1 +
>  include/linux/module.h            | 2 ++
>  kernel/module.c                   | 6 ++++++
>  3 files changed, 9 insertions(+)
> 
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index 69732d2..c55d8d9 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -468,6 +468,7 @@
>  #define KERNEL_CTORS()	. = ALIGN(8);			   \
>  			VMLINUX_SYMBOL(__ctors_start) = .; \
>  			*(.ctors)			   \
> +			*(.init_array)			   \

This is exactly how I (would) have done it.

>  			VMLINUX_SYMBOL(__ctors_end) = .;
>  #else
>  #define KERNEL_CTORS()
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 46f1ea0..89ff829 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -374,6 +374,8 @@ struct module
>  	/* Constructor functions. */
>  	ctor_fn_t *ctors;
>  	unsigned int num_ctors;
> +	ctor_fn_t *init_array;
> +	unsigned int num_init_array;

I think it would be safe to re-use the ctors-related fields here. Each GCC
version will only ever create either of .ctors or .init_array, but never
both. The only case where separate fields would be required, would be when
linking a kernel module from multiple object files compiled with different
versions of GCC.

>  #endif
>  };
>  #ifndef MODULE_ARCH_INIT
> diff --git a/kernel/module.c b/kernel/module.c
> index 2069158..581ae89 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -2760,6 +2760,9 @@ static void find_module_sections(struct module *mod, struct load_info *info)
>  #ifdef CONFIG_CONSTRUCTORS
>  	mod->ctors = section_objs(info, ".ctors",
>  				  sizeof(*mod->ctors), &mod->num_ctors);

When reusing mod->ctors, you could check for mod->ctors == NULL here and
fill in the values from section_objs(".init_array").

> +	mod->init_array = section_objs(info, ".init_array",
> +				  sizeof(*mod->init_array),
> +				  &mod->num_init_array);
>  #endif
> 
>  #ifdef CONFIG_TRACEPOINTS
> @@ -3024,6 +3027,9 @@ static void do_mod_ctors(struct module *mod)
> 
>  	for (i = 0; i < mod->num_ctors; i++)
>  		mod->ctors[i]();
> +
> +	for (i = 0; i < mod->num_init_array; i++)
> +		mod->init_array[i]();
>  #endif
>  }
> 

-- 
Peter Oberparleiter
Linux on System z Development - IBM Germany

  parent reply	other threads:[~2013-08-23 15:13 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23  8:39 [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 1/4] gcov: move gcov structs definitions to a gcc version specific file Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:09   ` Peter Oberparleiter
2013-08-23 15:09     ` Peter Oberparleiter
2013-08-23 16:50     ` Frantisek Hrbata
2013-08-23 16:50       ` Frantisek Hrbata
2013-08-26 12:17       ` Peter Oberparleiter
2013-08-23  8:39 ` [RFC PATCH 2/4] gcov: add support for gcc 4.7 gcov format Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:12   ` Peter Oberparleiter
2013-08-23 21:00     ` Frantisek Hrbata
2013-08-26 12:45       ` Peter Oberparleiter
2013-08-27 13:41         ` Frantisek Hrbata
2013-08-27 13:41           ` Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:15   ` Peter Oberparleiter
2013-08-23 15:21     ` Peter Oberparleiter
2013-08-24 19:44       ` Frantisek Hrbata
2013-08-25 18:29         ` Arnd Bergmann
2013-08-26 14:14         ` Peter Oberparleiter
2013-08-27 13:34           ` Frantisek Hrbata
2013-08-28 13:46             ` Peter Oberparleiter
2013-08-28 13:54               ` Frantisek Hrbata
2013-08-28 13:54                 ` Frantisek Hrbata
2013-08-24 19:12     ` Frantisek Hrbata
2013-08-24 19:12       ` Frantisek Hrbata
2013-08-26 12:56       ` Peter Oberparleiter
2013-08-26 12:56         ` Peter Oberparleiter
2013-08-27 13:23         ` Frantisek Hrbata
2013-08-27 13:23           ` Frantisek Hrbata
2013-08-23  8:39 ` [RFC PATCH 4/4] kernel: add support for init_array constructors Frantisek Hrbata
2013-08-23  8:39   ` Frantisek Hrbata
2013-08-23 15:13   ` Peter Oberparleiter [this message]
2013-08-23 16:55     ` Frantisek Hrbata
2013-08-23 15:08 ` [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Peter Oberparleiter
2013-08-23 16:15   ` Frantisek Hrbata
2013-08-23 16:15     ` Frantisek Hrbata
2013-08-26 11:39     ` LF.Tan
2013-08-26 11:39       ` LF.Tan
2013-08-26 14:19       ` Peter Oberparleiter
2013-08-27  2:38         ` LF.Tan
2013-08-26 11:57     ` Peter Oberparleiter

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=52177C1B.60107@linux.vnet.ibm.com \
    --to=oberpar@linux.vnet.ibm.com \
    --cc=agospoda@redhat.com \
    --cc=arnd@arndb.de \
    --cc=fhrbata@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgahagan@redhat.com \
    --cc=rusty@rustcorp.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).