From: Andre Przywara <andre.przywara@arm.com>
To: Will Deacon <will@kernel.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
Marc Zyngier <maz@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: [PATCH kvmtool v2 21/22] hw/serial: ARM/arm64: Use MMIO at higher addresses
Date: Thu, 25 Feb 2021 00:59:14 +0000 [thread overview]
Message-ID: <20210225005915.26423-22-andre.przywara@arm.com> (raw)
In-Reply-To: <20210225005915.26423-1-andre.przywara@arm.com>
Using the UART devices at their legacy I/O addresses as set by IBM in
1981 was a kludge we used for simplicity on ARM platforms as well.
However this imposes problems due to their missing alignment and overlap
with the PCI I/O address space.
Now that we can switch a device easily between using ioports and MMIO,
let's move the UARTs out of the first 4K of memory on ARM platforms.
That should be transparent for well behaved guests, since the change is
naturally reflected in the device tree. Even "earlycon" keeps working,
as the stdout-path property is adjusted automatically.
People providing direct earlycon parameters via the command line need to
adjust it to: "earlycon=uart,mmio,0x1000000".
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
---
arm/include/arm-common/kvm-arch.h | 3 +++
hw/serial.c | 45 ++++++++++++++++++++-----------
2 files changed, 32 insertions(+), 16 deletions(-)
diff --git a/arm/include/arm-common/kvm-arch.h b/arm/include/arm-common/kvm-arch.h
index b12255b0..633ea8fa 100644
--- a/arm/include/arm-common/kvm-arch.h
+++ b/arm/include/arm-common/kvm-arch.h
@@ -28,6 +28,9 @@
#define ARM_IOPORT_SIZE (1U << 16)
+#define ARM_UART_MMIO_BASE ARM_MMIO_AREA
+#define ARM_UART_MMIO_SIZE 0x10000
+
#define KVM_FLASH_MMIO_BASE (ARM_MMIO_AREA + 0x1000000)
#define KVM_FLASH_MAX_SIZE 0x1000000
diff --git a/hw/serial.c b/hw/serial.c
index 4be188a1..1854add2 100644
--- a/hw/serial.c
+++ b/hw/serial.c
@@ -13,6 +13,17 @@
#include <pthread.h>
+#if defined(CONFIG_ARM) || defined(CONFIG_ARM64)
+#define serial_iobase(nr) (ARM_UART_MMIO_BASE + (nr) * 0x1000)
+#define serial_irq(nr) (32 + (nr))
+#define SERIAL8250_BUS_TYPE DEVICE_BUS_MMIO
+#else
+#define serial_iobase(nr) ((((nr) & 1) ? 0x200 : 0x300) + \
+ ((nr) >= 2 ? 0xe8 : 0xf8))
+#define serial_irq(nr) (((nr) & 1) ? 3 : 4)
+#define SERIAL8250_BUS_TYPE DEVICE_BUS_IOPORT
+#endif
+
/*
* This fakes a U6_16550A. The fifo len needs to be 64 as the kernel
* expects that for autodetection.
@@ -27,7 +38,7 @@ struct serial8250_device {
struct mutex mutex;
u8 id;
- u16 iobase;
+ u32 iobase;
u8 irq;
u8 irq_state;
int txcnt;
@@ -65,56 +76,56 @@ static struct serial8250_device devices[] = {
/* ttyS0 */
[0] = {
.dev_hdr = {
- .bus_type = DEVICE_BUS_IOPORT,
+ .bus_type = SERIAL8250_BUS_TYPE,
.data = serial8250_generate_fdt_node,
},
.mutex = MUTEX_INITIALIZER,
.id = 0,
- .iobase = 0x3f8,
- .irq = 4,
+ .iobase = serial_iobase(0),
+ .irq = serial_irq(0),
SERIAL_REGS_SETTING
},
/* ttyS1 */
[1] = {
.dev_hdr = {
- .bus_type = DEVICE_BUS_IOPORT,
+ .bus_type = SERIAL8250_BUS_TYPE,
.data = serial8250_generate_fdt_node,
},
.mutex = MUTEX_INITIALIZER,
.id = 1,
- .iobase = 0x2f8,
- .irq = 3,
+ .iobase = serial_iobase(1),
+ .irq = serial_irq(1),
SERIAL_REGS_SETTING
},
/* ttyS2 */
[2] = {
.dev_hdr = {
- .bus_type = DEVICE_BUS_IOPORT,
+ .bus_type = SERIAL8250_BUS_TYPE,
.data = serial8250_generate_fdt_node,
},
.mutex = MUTEX_INITIALIZER,
.id = 2,
- .iobase = 0x3e8,
- .irq = 4,
+ .iobase = serial_iobase(2),
+ .irq = serial_irq(2),
SERIAL_REGS_SETTING
},
/* ttyS3 */
[3] = {
.dev_hdr = {
- .bus_type = DEVICE_BUS_IOPORT,
+ .bus_type = SERIAL8250_BUS_TYPE,
.data = serial8250_generate_fdt_node,
},
.mutex = MUTEX_INITIALIZER,
.id = 3,
- .iobase = 0x2e8,
- .irq = 3,
+ .iobase = serial_iobase(3),
+ .irq = serial_irq(3),
SERIAL_REGS_SETTING
},
@@ -439,7 +450,8 @@ static int serial8250__device_init(struct kvm *kvm,
return r;
ioport__map_irq(&dev->irq);
- r = kvm__register_pio(kvm, dev->iobase, 8, serial8250_mmio, dev);
+ r = kvm__register_iotrap(kvm, dev->iobase, 8, serial8250_mmio, dev,
+ SERIAL8250_BUS_TYPE);
return r;
}
@@ -462,7 +474,7 @@ cleanup:
for (j = 0; j <= i; j++) {
struct serial8250_device *dev = &devices[j];
- kvm__deregister_pio(kvm, dev->iobase);
+ kvm__deregister_iotrap(kvm, dev->iobase, SERIAL8250_BUS_TYPE);
device__unregister(&dev->dev_hdr);
}
@@ -478,7 +490,8 @@ int serial8250__exit(struct kvm *kvm)
for (i = 0; i < ARRAY_SIZE(devices); i++) {
struct serial8250_device *dev = &devices[i];
- r = kvm__deregister_pio(kvm, dev->iobase);
+ r = kvm__deregister_iotrap(kvm, dev->iobase,
+ SERIAL8250_BUS_TYPE);
if (r < 0)
return r;
device__unregister(&dev->dev_hdr);
--
2.17.5
next prev parent reply other threads:[~2021-02-25 1:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 0:58 [PATCH kvmtool v2 00/22] Unify I/O port and MMIO trap handling Andre Przywara
2021-02-25 0:58 ` [PATCH kvmtool v2 01/22] ioport: Remove ioport__setup_arch() Andre Przywara
2021-03-02 18:02 ` Alexandru Elisei
2021-02-25 0:58 ` [PATCH kvmtool v2 02/22] hw/serial: Use device abstraction for FDT generator function Andre Przywara
2021-02-25 0:58 ` [PATCH kvmtool v2 03/22] ioport: Retire .generate_fdt_node functionality Andre Przywara
2021-02-25 0:58 ` [PATCH kvmtool v2 04/22] mmio: Extend handling to include ioport emulation Andre Przywara
2021-03-03 17:58 ` Alexandru Elisei
2021-03-15 12:24 ` Andre Przywara
2021-02-25 0:58 ` [PATCH kvmtool v2 05/22] hw/i8042: Clean up data types Andre Przywara
2021-02-25 0:58 ` [PATCH kvmtool v2 06/22] hw/i8042: Refactor trap handler Andre Przywara
2021-03-08 17:16 ` Alexandru Elisei
2021-02-25 0:59 ` [PATCH kvmtool v2 07/22] hw/i8042: Switch to new trap handlers Andre Przywara
2021-03-08 17:22 ` Alexandru Elisei
2021-02-25 0:59 ` [PATCH kvmtool v2 08/22] x86/ioport: Refactor " Andre Przywara
2021-03-09 11:49 ` Alexandru Elisei
2021-03-15 12:26 ` Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 09/22] x86/ioport: Switch to new " Andre Przywara
2021-03-09 12:09 ` Alexandru Elisei
2021-03-15 12:26 ` Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 10/22] hw/rtc: Refactor " Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 11/22] hw/rtc: Switch to new trap handler Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 12/22] hw/vesa: Switch trap handling to use MMIO handler Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 13/22] hw/serial: Refactor trap handler Andre Przywara
2021-03-12 11:29 ` Alexandru Elisei
2021-03-15 12:26 ` Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 14/22] hw/serial: Switch to new trap handlers Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 15/22] vfio: Refactor ioport trap handler Andre Przywara
2021-03-09 14:21 ` Alexandru Elisei
2021-02-25 0:59 ` [PATCH kvmtool v2 16/22] vfio: Switch to new ioport trap handlers Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 17/22] virtio: Switch trap handling to use MMIO handler Andre Przywara
2021-03-09 14:43 ` Alexandru Elisei
2021-02-25 0:59 ` [PATCH kvmtool v2 18/22] pci: " Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 19/22] Remove ioport specific routines Andre Przywara
2021-03-09 15:13 ` Alexandru Elisei
2021-02-25 0:59 ` [PATCH kvmtool v2 20/22] arm: Reorganise and document memory map Andre Przywara
2021-03-09 15:46 ` Alexandru Elisei
2021-03-15 12:27 ` Andre Przywara
2021-02-25 0:59 ` Andre Przywara [this message]
2021-03-09 16:02 ` [PATCH kvmtool v2 21/22] hw/serial: ARM/arm64: Use MMIO at higher addresses Alexandru Elisei
2021-03-15 12:27 ` Andre Przywara
2021-02-25 0:59 ` [PATCH kvmtool v2 22/22] hw/rtc: " Andre Przywara
2021-03-09 16:06 ` Alexandru Elisei
2021-03-02 17:57 ` [PATCH kvmtool v2 00/22] Unify I/O port and MMIO trap handling Alexandru Elisei
2021-03-03 18:41 ` Andre Przywara
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=20210225005915.26423-22-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=sami.mujawar@arm.com \
--cc=will@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