From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] x86/earlyprintk: setup earlyprintk as early as possible
Date: Wed, 8 Apr 2015 15:31:06 +0600 [thread overview]
Message-ID: <1428485466-24326-1-git-send-email-kuleshovmail@gmail.com> (raw)
As setup_early_printk passed to the early_param, it will be usable only after
'parse_early_param' function will be called from the 'setup_arch'. So we have
earlyprintk during early boot and decompression. Next point after decompression
of the kernel where we can use early_printk is after call of the
'parse_early_param'.
This patch provides initialization of earlyprintk serial console as early
as possible in the arch/x86/kerne/head{32,64}.c
Alexander Kuleshov (2):
x86/setup: update boot_command_line with builtin_cmdline in separate
function
x86/earlyprintk: setup earlyprintk as early as possible
arch/x86/kernel/early_printk.c | 2 +-
arch/x86/kernel/head.c | 14 ++++++++++++++
arch/x86/kernel/head32.c | 3 +++
arch/x86/kernel/head64.c | 8 +++++++-
arch/x86/kernel/setup.c | 31 ++++++++++++++++++-------------
include/linux/init.h | 6 +++++-
include/linux/printk.h | 4 ++++
kernel/printk/printk.c | 11 +++++++----
8 files changed, 59 insertions(+), 20 deletions(-)
--
2.3.3.611.g09038fc.dirty
next reply other threads:[~2015-04-08 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 9:31 Alexander Kuleshov [this message]
2015-04-08 9:31 ` [PATCH 1/2] x86/setup: update boot_command_line with builtin_cmdline in separate function Alexander Kuleshov
2015-04-08 9:31 ` [PATCH 2/2] x86/earlyprintk: setup earlyprintk as early as possible Alexander Kuleshov
2015-04-08 11:32 ` Peter Hurley
2015-04-09 7:39 ` Alexander Kuleshov
2015-05-10 19:13 [PATCH 0/2] " Alexander Kuleshov
2015-05-11 7:27 ` Andy Shevchenko
2015-05-11 9:56 ` Alexander Kuleshov
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=1428485466-24326-1-git-send-email-kuleshovmail@gmail.com \
--to=kuleshovmail@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®