From: sergey.senozhatsky@gmail.com (Sergey Senozhatsky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 4/6] init: allow initcall tables to be emitted using relative references
Date: Wed, 27 Jun 2018 23:20:53 +0900 [thread overview]
Message-ID: <20180627142053.GB477@tigerII.localdomain> (raw)
In-Reply-To: <20180626182802.19932-5-ard.biesheuvel@linaro.org>
On (06/26/18 20:27), Ard Biesheuvel wrote:
> /*
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index 247808333ba4..688a27b0888c 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2772,7 +2772,8 @@ EXPORT_SYMBOL(unregister_console);
> void __init console_init(void)
> {
> int ret;
> - initcall_t *call;
> + initcall_t call;
> + initcall_entry_t *ce;
>
> /* Setup the default TTY line discipline. */
> n_tty_init();
> @@ -2781,13 +2782,14 @@ void __init console_init(void)
> * set up the console device so that later boot sequences can
> * inform about problems etc..
> */
> - call = __con_initcall_start;
> + ce = __con_initcall_start;
> trace_initcall_level("console");
> - while (call < __con_initcall_end) {
> - trace_initcall_start((*call));
> - ret = (*call)();
> - trace_initcall_finish((*call), ret);
> - call++;
> + while (ce < __con_initcall_end) {
> + call = initcall_from_entry(ce);
> + trace_initcall_start(call);
> + ret = call();
> + trace_initcall_finish(call, ret);
> + ce++;
> }
> }
printk bits look OK to me.
The patch set works fine on my x86_64 and does reduce the size of vmlinux.
Acked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-ss
next prev parent reply other threads:[~2018-06-27 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 18:27 [PATCH v9 0/6] add support for relative references in special sections Ard Biesheuvel
2018-06-26 18:27 ` [PATCH v9 1/6] arch: enable relative relocations for arm64, power and x86 Ard Biesheuvel
2018-06-26 18:27 ` [PATCH v9 2/6] module: allow symbol exports to be disabled Ard Biesheuvel
2018-06-26 18:27 ` [PATCH v9 3/6] module: use relative references for __ksymtab entries Ard Biesheuvel
2018-06-27 15:13 ` Will Deacon
2018-06-27 15:21 ` Ard Biesheuvel
2018-06-26 18:27 ` [PATCH v9 4/6] init: allow initcall tables to be emitted using relative references Ard Biesheuvel
2018-06-26 19:13 ` James Morris
2018-06-27 14:20 ` Sergey Senozhatsky [this message]
2018-06-27 15:22 ` Petr Mladek
2018-06-30 10:16 ` kbuild test robot
2018-06-26 18:28 ` [PATCH v9 5/6] PCI: Add support for relative addressing in quirk tables Ard Biesheuvel
2018-06-26 18:28 ` [PATCH v9 6/6] kernel: tracepoints: add support for relative references Ard Biesheuvel
2018-06-27 5:33 ` [PATCH v9 0/6] add support for relative references in special sections Michael Ellerman
2018-06-27 15:15 ` Will Deacon
2018-07-01 17:39 ` Ard Biesheuvel
2018-07-03 8:38 ` Ingo Molnar
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=20180627142053.GB477@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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