mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
	Jiri Slaby <jslaby@suse.com>,
	Peter Hurley <peter@hurleysoftware.com>,
	andriy.shevchenko@linux.intel.com, phillip.raffeck@fau.de,
	anton.wuerfel@fau.de, yamada.masahiro@socionext.com,
	valentinrothberg@gmail.com, linux-serial@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ddutile@redhat.com
Subject: Re: [PATCH] 8250: Hypervisors always export working 16550A UARTs.
Date: Fri, 29 Apr 2016 08:15:40 -0700	[thread overview]
Message-ID: <20160429151540.GA16895@kroah.com> (raw)
In-Reply-To: <20160429074114.GC3826@redhat.com>

On Fri, Apr 29, 2016 at 08:41:14AM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 29, 2016 at 10:01:08AM +0300, Matwey V. Kornilov wrote:
> > 2016-04-29 1:18 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>:
> > > [This is an opinionated patch, mainly for discussion.]
> > >
> > > I'm trying to reduce the time taken in the kernel in initcalls, with
> > > my aim being to reduce the current ~700ms spent in initcalls before
> > > userspace, down to something like 100ms.  All times on my Broadwell-U
> > > laptop, under virtualization.  The purpose of this is to be able to
> > > launch VMs around containers with minimal overhead, like Intel Clear
> > > Containers, but using standard distro kernels and qemu.
> > >
> > > Currently the kernel spends 25ms inspecting the UART that we passed to
> > > it from qemu to find out whether it's an 8250/16550/16550A perhaps
> > > with a non-working FIFO or other quirks.  Well, it isn't -- it's a
> > > working emulated 16550A, with a FIFO and no quirks, and if it isn't,
> > > we should fix qemu.
> > >
> > > So the patch detects if we're running virtualized (perhaps it should
> > > only check for qemu/KVM?) and if so, shortcuts the tests.
> > 
> > Does anybody know, whether it is possible to pass through real
> > hardware serial port to a guest? It seems to be as simple as to pass
> > through an interrupt and memory IO ports.
> 
> In theory it seems like something VFIO could do.  Passing something as
> low performance as a serial port through would seem to make little
> sense though.

Multi-port serial PCI cards are not "low performance" and might be
passed through directly to a guest.

thanks,

greg k-h

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 22:18 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
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 [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=20160429151540.GA16895@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®