All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: jslaby@suse.com, peter@hurleysoftware.com,
	andriy.shevchenko@linux.intel.com, phillip.raffeck@fau.de,
	anton.wuerfel@fau.de, yamada.masahiro@socionext.com,
	matwey@sai.msu.ru, valentinrothberg@gmail.com,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	ddutile@redhat.com
Subject: Re: [PATCH] 8250: Hypervisors always export working 16550A UARTs.
Date: Fri, 29 Apr 2016 10:32:02 -0700	[thread overview]
Message-ID: <20160429173202.GA9134@kroah.com> (raw)
In-Reply-To: <20160429160256.GE28599@redhat.com>

On Fri, Apr 29, 2016 at 05:02:57PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 29, 2016 at 08:54:13AM -0700, Greg KH wrote:
> > You are trying to take a generalized kernel and somehow "know" about the
> > hardware ahead of time it is going to run on.  That seems like two
> > conflicting requirements, don't you agree?
> 
> We would have the 8250 serial port in any kernel.  Even if Fedora
> kernel maintainers allowed us to have specialized kernels for each
> purpose, I would use the simple ISA serial port here because it allows
> us to capture debug messages very early in the boot.  Alternatives
> like virtio-console don't allow that.
> 
> The kernel does know what hardware it's running on - via the CPUID
> hypervisor leaf.  It's also possible for us to tell the kernel about
> the hardware using the command line, ACPI[*], DT, etc.  I'd really
> like to tell the kernel this is a 16550A, not broken, you don't need
> to spend time testing that.

Then properly describe the device to the kernel in a way that you know
you don't have to do the 20ms sleep from your system configuration file
(acpi, dt, etc.)

good luck,

greg k-h

  reply	other threads:[~2016-04-29 17:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 22:18 [PATCH] 8250: Hypervisors always export working 16550A UARTs Richard W.M. Jones
2016-04-28 22:18 ` Richard W.M. Jones
2016-04-28 22:56   ` Greg KH
2016-04-29  8:10     ` Richard W.M. Jones
2016-04-29 15:16       ` Greg KH
2016-04-29 15:37         ` Richard W.M. Jones
2016-04-29 15:54           ` Greg KH
2016-04-29 16:02             ` Richard W.M. Jones
2016-04-29 17:32               ` Greg KH [this message]
2016-04-29 18:14           ` Don Dutile
2016-04-29  0:04 ` Peter Hurley
2016-04-29  7:01 ` Matwey V. Kornilov
2016-04-29  7:41   ` Richard W.M. Jones
2016-04-29 15:15     ` Greg KH

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=20160429173202.GA9134@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anton.wuerfel@fau.de \
    --cc=ddutile@redhat.com \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=matwey@sai.msu.ru \
    --cc=peter@hurleysoftware.com \
    --cc=phillip.raffeck@fau.de \
    --cc=rjones@redhat.com \
    --cc=valentinrothberg@gmail.com \
    --cc=yamada.masahiro@socionext.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.