public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	David Cohen <david.a.cohen@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alan Cox <alan@linux.intel.com>,
	"Stuart R. Anderson" <stuart.r.anderson@intel.com>
Subject: Re: [RFC][PATCH] x86: Allow early_printk to use console style param like 115200n8
Date: Sat, 4 Jul 2015 13:03:59 +0200	[thread overview]
Message-ID: <20150704110359.GA18107@gmail.com> (raw)
In-Reply-To: <20150703181643.4fd4053d@grimm.local.home>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> When I enable early_printk on a kernel, I cut and paste the console=
> input and add to earlyprintk parameter. But I notice recently that
> ktest has not been detecting triple faults. The way it detects it, is
> by seeing the kernel banner "Linux version .." with a different kernel
> version pop up. Then I noticed that early printk was no longer working
> on my console, which was why ktest was not seeing it.
> 
> I bisected it down and it was added to 4.0 with this commit:
> 
> commit ea9e9d802902 ("Specify PCI based UART for earlyprintk")

Ugh, this commit changed x86 code but was not Cc:-ed to any x86 maintainer, and 
the title was pretty misleading as well...

( That patch should have been split into at least two parts: the generic 
  earlyprintk changes affecting all modes, and the 'pciserial' enablement. Anyway, 
  that's water down the bridge. )

> because it converted the simple_strtoul() that converts the baud number into a 
> kstrtoul(). The problem with this is, I had as my baud rate, 115200n8 
> (acceptable for console=ttyS0), but because of the "n8", the kstrtoul() doesn't 
> parse the baud rate and returns an error, which sets the baud rate to the 
> default 9600. This explains the garbage on my screen.

ugh. I bet it also breaks the earlyprintk=ttyS0..,keep format?

> Now, earlyprintk= kernel parameter does not say it accepts that format. Thus, 
> one answer would simply be me changing my kernel parameters to remove the "n8" 
> since it isn't parsed anyway. But I wonder if other people run into this, and it 
> seems strange that the two consoles for serial accepts different input.

So why not revert to the known-working simple_strtoul()? I don't see this as an 
improvement:

> +		/*
> +		 * In case the input is like console with text after the baud
> +		 * rate. e.g. 115200n8. kstrtoul() will error on such input.
> +		 */
> +		for (p = s; *p && isdigit(*p); p++)
> +			;
> +		*p = 0;
> +
>  		if (kstrtoul(s, 0, &baud) < 0 || baud == 0)
>  			baud = DEFAULT_BAUD;


Over the old:

		baud = simple_strtoul(s, &e, 0);

Thanks,

	Ingo

  reply	other threads:[~2015-07-05  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 22:16 [RFC][PATCH] x86: Allow early_printk to use console style param like 115200n8 Steven Rostedt
2015-07-04 11:03 ` Ingo Molnar [this message]
2015-07-04 13:16   ` Steven Rostedt
2015-07-04 13:20   ` Steven Rostedt
2015-07-05  9:05     ` Ingo Molnar
2015-07-06 13:29     ` Peter Hurley
2015-07-06 13:33       ` Ingo Molnar
2015-07-06 14:14 ` [PATCH] " Steven Rostedt
2015-07-06 16:34   ` [tip:x86/urgent] x86/earlyprintk: Allow early_printk() to use console style parameters like '115200n8' tip-bot for Steven Rostedt

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=20150704110359.GA18107@gmail.com \
    --to=mingo@kernel.org \
    --cc=alan@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david.a.cohen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stuart.r.anderson@intel.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