linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: gregkh@linuxfoundation.org
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: [PATCH] 8250: Hypervisors always export working 16550A UARTs.
Date: Thu, 28 Apr 2016 23:18:33 +0100	[thread overview]
Message-ID: <1461881913-23967-2-git-send-email-rjones@redhat.com> (raw)
In-Reply-To: <1461881913-23967-1-git-send-email-rjones@redhat.com>

Currently autoconf spends 25ms (on my laptop) testing if the UART
exported to it by KVM is an 8250 without FIFO and/or with strange
quirks, which it obviously isn't.  Assume it is exported to us by a
hypervisor, it's a normal, working 16550A.

Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
---
 drivers/tty/serial/8250/8250_port.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
index 00ad2637..de19924 100644
--- a/drivers/tty/serial/8250/8250_port.c
+++ b/drivers/tty/serial/8250/8250_port.c
@@ -1171,6 +1171,13 @@ static void autoconfig(struct uart_8250_port *up)
 	if (!port->iobase && !port->mapbase && !port->membase)
 		return;
 
+	/* Hypervisors always export working 16550A devices. */
+	if (cpu_has_hypervisor) {
+		up->port.type = PORT_16550A;
+		up->capabilities |= UART_CAP_FIFO;
+		return;
+	}
+
 	DEBUG_AUTOCONF("ttyS%d: autoconf (0x%04lx, 0x%p): ",
 		       serial_index(port), port->iobase, port->membase);
 
-- 
2.7.4

  reply	other threads:[~2016-04-28 22:18 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 [this message]
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

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=1461881913-23967-2-git-send-email-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anton.wuerfel@fau.de \
    --cc=ddutile@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --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=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;
as well as URLs for NNTP newsgroup(s).