From: Ingo Molnar <mingo@kernel.org>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/earlyprintk: setup earlyprintk as early as possible
Date: Tue, 7 Apr 2015 12:24:45 +0200 [thread overview]
Message-ID: <20150407102445.GA13658@gmail.com> (raw)
In-Reply-To: <CANCZXo5Fx5rTYWNRrC4T7nkPzB9iVn7EnYpXUCTsDXxW34TwyQ@mail.gmail.com>
* Alexander Kuleshov <kuleshovmail@gmail.com> wrote:
> 2015-04-07 15:52 GMT+06:00 Ingo Molnar <mingo@kernel.org>:
> >
> > It would be nice to test it via a well placed printk() and check that
> > before the patch the message doesn't go to the serial console and
> > after the patch the message indeed arrives on the early serial console
> > - or something like that.
>
> I have tested this patch when i wrote it and early_printk does not print
> anything before the parse_early_param. But i don't know how to show this
> in code in a correct way. [...]
Just add a debug printk() for your own testing, right after the param
initialization call, to be confident that the early console indeed
works.
> which i removed in the previous patch
> (https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=91d8f0416f3989e248d3a3d3efb821eda10a85d2)?
>
> Any one another question about this. I submited patch only for
> head64.c and it does not affect kernel for i386, because i'm not
> sure where is the best place to setup earlyprintk in the head32.c. I
> thought to put it in the start of i386_start_kernel(void) (from
> head32.c) but not sure about it.
I'd use i386_start_kernel() on 32-bit and x86_64_start_kernel() on
64-bit - but I haven't tested whether it actually works.
Thanks,
Ingo
next prev parent reply other threads:[~2015-04-07 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 13:17 [PATCH] x86/earlyprintk: setup earlyprintk as early as possible Alexander Kuleshov
2015-04-07 9:52 ` Ingo Molnar
2015-04-07 10:19 ` Alexander Kuleshov
2015-04-07 10:24 ` Ingo Molnar [this message]
2015-04-07 10:31 ` Alexander Kuleshov
2015-04-07 10:33 ` Ingo Molnar
2015-04-07 19:07 ` Yinghai Lu
2015-04-07 19:08 ` Yinghai Lu
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=20150407102445.GA13658@gmail.com \
--to=mingo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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