From: Borislav Petkov <bp@suse.de>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rustad <mark.d.rustad@intel.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH v5 2/2] x86/earlyprintk: setup earlyprintk as early as possible
Date: Mon, 11 May 2015 12:24:10 +0200 [thread overview]
Message-ID: <20150511102409.GC15278@pd.tnic> (raw)
In-Reply-To: <1431338958-25864-1-git-send-email-kuleshovmail@gmail.com>
On Mon, May 11, 2015 at 04:09:18PM +0600, Alexander Kuleshov wrote:
> The early_printk function is usable after setup_early_printk will be executed. We
> pass 'earlyprintk' through the kernel command line. It means that earlyprintk
> will be usable only after the 'parse_early_param' will be executed. So we have
> usable earlyprintk only during early boot, kernel decompression and after call
> of the 'parse_early_param'.
>
> This patch makes setup_early_printk visible for head{32,64}.c So 'early_printk'
> function will be usabable after decompression of the kernel and before
> parse_early_param will be called. It also safe if CONFIG_CMDLINE_BOOL
> and CONFIG_CMDLINE_OVERRIDE are set, because setup_cmdline function will be
> called before the setup_early_printk.
>
> Tested it with qemu, so early_printk() is usable and prints to serial console
> right after setup_early_printk function called from arch/x86/kerne/head64.c
>
> Signed-off-by: Alexander Kuleshov <kuleshovmail@gmail.com>
> ---
> arch/x86/include/asm/serial.h | 2 ++
> arch/x86/kernel/early_printk.c | 25 +++++++++++++++++++++++++
> arch/x86/kernel/head32.c | 5 +++++
> arch/x86/kernel/head64.c | 8 +++++++-
> 4 files changed, 39 insertions(+), 1 deletion(-)
Also, when you send the patches, send them to yourself first and try
applying them. This way you can check whether your sending path doesn't
mangle them for some reason.
And ditto:
ERROR: code indent should use tabs where possible
#91: FILE: arch/x86/kernel/head32.c:35:
+ setup_early_serial_console();$
WARNING: please, no spaces at the start of a line
#91: FILE: arch/x86/kernel/head32.c:35:
+ setup_early_serial_console();$
ERROR: code indent should use tabs where possible
#94: FILE: arch/x86/kernel/head32.c:38:
+ early_printk("Kernel alive\n");$
WARNING: please, no spaces at the start of a line
#94: FILE: arch/x86/kernel/head32.c:38:
+ early_printk("Kernel alive\n");$
total: 2 errors, 3 warnings, 66 lines checked
NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
scripts/cleanfile
Your patch has style problems, please review.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-05-11 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 10:08 [PATCH RESEND v5 0/2] x86/earlyprintk: setup earlyprintk as early as possible Alexander Kuleshov
2015-05-11 10:09 ` [PATCH v2 1/2] x86/setup: introduce setup_bultin_cmdline Alexander Kuleshov
2015-05-11 10:21 ` Borislav Petkov
2015-05-11 10:36 ` Andy Shevchenko
2015-05-11 10:09 ` [PATCH v5 2/2] x86/earlyprintk: setup earlyprintk as early as possible Alexander Kuleshov
2015-05-11 10:24 ` Borislav Petkov [this message]
2015-05-11 10:39 ` [PATCH RESEND v5 0/2] " Andy Shevchenko
2015-05-12 8:08 ` [PATCH v6 0/3] Alexander Kuleshov
2015-05-12 8:09 ` [PATCH v3 1/3] x86/setup: introduce setup_bultin_cmdline Alexander Kuleshov
2015-05-12 10:50 ` Andy Shevchenko
2015-05-12 16:14 ` Alexander Kuleshov
2015-05-12 17:52 ` Andy Shevchenko
2015-05-12 8:09 ` [PATCH v1 2/3] x86/setup: handle builtin command line as early as possible Alexander Kuleshov
2015-05-12 8:10 ` [PATCH v6 3/3] x86/earlyprintk: setup earlyprintk " Alexander Kuleshov
2015-05-12 11:19 ` Andy Shevchenko
2015-05-12 16:26 ` Alexander Kuleshov
2015-05-12 17:58 ` Andy Shevchenko
2015-05-12 18:08 ` 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=20150511102409.GC15278@pd.tnic \
--to=bp@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--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