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 v10 3/3] x86/earlyprintk: setup earlyprintk as early as possible
Date: Tue, 9 Jun 2015 11:43:48 +0200 [thread overview]
Message-ID: <20150609094348.GB22105@pd.tnic> (raw)
In-Reply-To: <CANCZXo7dFM9GSAyzpoy7gTFpS=viVxTN43F4LgZW7YkFEzcjzg@mail.gmail.com>
On Tue, Jun 09, 2015 at 03:19:38PM +0600, Alexander Kuleshov wrote:
> I've tested this and does not see early_printk output too on the
> hardware, but only with qemu when I setup serial connection... The
> problem here that the early_printk function does not use the log_buf
> to store its messages as it printk does.
>
> How to be with this?
Well, as I said, you'd need to do more staring. You need to find out
why it doesn't work. If it fixable, then fix it. Remember, you want for
early_printk() to work that early.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2015-06-09 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 14:13 [PATCH v10 0/3] x86/earlyprintk: setup serial earlyprintk as early as possible Alexander Kuleshov
2015-06-07 14:14 ` [PATCH v10 1/3] x86/setup: introduce setup_bultin_cmdline Alexander Kuleshov
2015-06-07 14:14 ` [PATCH v10 2/3] x86/setup: handle builtin command line as early as possible Alexander Kuleshov
2015-06-07 14:14 ` [PATCH v10 3/3] x86/earlyprintk: setup earlyprintk " Alexander Kuleshov
2015-06-08 9:33 ` Borislav Petkov
2015-06-09 9:19 ` Alexander Kuleshov
2015-06-09 9:43 ` Borislav Petkov [this message]
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=20150609094348.GB22105@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