From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Andre Przywara <andre.przywara@arm.com>,
Will Deacon <will@kernel.org>,
Julien Thierry <julien.thierry.kdev@gmail.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
Marc Zyngier <maz@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: Re: [PATCH kvmtool v3 21/22] hw/serial: ARM/arm64: Use MMIO at higher addresses
Date: Wed, 17 Mar 2021 16:17:32 +0000 [thread overview]
Message-ID: <7ce22c90-bf5c-b976-5698-85a7605bc1b7@arm.com> (raw)
In-Reply-To: <20210315153350.19988-22-andre.przywara@arm.com>
Hi Andre,
On 3/15/21 3:33 PM, Andre Przywara wrote:
> 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".
Checked and that's indeed the address of the first UART.
>
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> arm/include/arm-common/kvm-arch.h | 7 ++--
> hw/serial.c | 54 +++++++++++++++++++++----------
> 2 files changed, 42 insertions(+), 19 deletions(-)
>
> diff --git a/arm/include/arm-common/kvm-arch.h b/arm/include/arm-common/kvm-arch.h
> index a2e32953..bf34d742 100644
> --- a/arm/include/arm-common/kvm-arch.h
> +++ b/arm/include/arm-common/kvm-arch.h
> @@ -13,8 +13,8 @@
> * 0 64K 16M 32M 48M 1GB 2GB
> * +-------+----+-------+-------+--------+-----+---------+---......
> * | PCI |////| plat | | | | |
> - * | I/O |////| MMIO | Flash | virtio | GIC | PCI | DRAM
> - * | space |////| | | MMIO | | (AXI) |
> + * | I/O |////| MMIO: | Flash | virtio | GIC | PCI | DRAM
> + * | space |////| UART | | MMIO | | (AXI) |
> * | |////| | | | | |
> * +-------+----+-------+-------+--------+-----+---------+---......
> */
> @@ -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 16af493b..3d533623 100644
> --- a/hw/serial.c
> +++ b/hw/serial.c
> @@ -13,6 +13,24 @@
>
> #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_0 (KVM_IOPORT_AREA + 0x3f8)
> +#define serial_iobase_1 (KVM_IOPORT_AREA + 0x2f8)
> +#define serial_iobase_2 (KVM_IOPORT_AREA + 0x3e8)
> +#define serial_iobase_3 (KVM_IOPORT_AREA + 0x2e8)
> +#define serial_irq_0 4
> +#define serial_irq_1 3
> +#define serial_irq_2 4
> +#define serial_irq_3 3
> +#define serial_iobase(nr) serial_iobase_##nr
> +#define serial_irq(nr) serial_irq_##nr
> +#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 +45,7 @@ struct serial8250_device {
> struct mutex mutex;
> u8 id;
>
> - u16 iobase;
> + u32 iobase;
> u8 irq;
> u8 irq_state;
> int txcnt;
> @@ -65,56 +83,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
> },
> @@ -407,7 +425,7 @@ void serial8250_generate_fdt_node(void *fdt, struct device_header *dev_hdr,
> struct serial8250_device,
> dev_hdr);
>
> - u64 addr = KVM_IOPORT_AREA + dev->iobase;
> + u64 addr = dev->iobase;
> u64 reg_prop[] = {
> cpu_to_fdt64(addr),
> cpu_to_fdt64(8),
> @@ -440,7 +458,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;
> }
> @@ -463,7 +482,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);
> }
>
> @@ -479,7 +498,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);
Looks good to me:
Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>
Thanks,
Alex
next prev parent reply other threads:[~2021-03-17 16:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:33 [PATCH kvmtool v3 00/22] Unify I/O port and MMIO trap handling Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 01/22] ioport: Remove ioport__setup_arch() Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 02/22] hw/serial: Use device abstraction for FDT generator function Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 03/22] ioport: Retire .generate_fdt_node functionality Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 04/22] mmio: Extend handling to include ioport emulation Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 05/22] hw/i8042: Clean up data types Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 06/22] hw/i8042: Refactor trap handler Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 07/22] hw/i8042: Switch to new trap handlers Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 08/22] x86/ioport: Refactor " Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 09/22] x86/ioport: Switch to new " Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 10/22] hw/rtc: Refactor " Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 11/22] hw/rtc: Switch to new trap handler Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 12/22] hw/vesa: Switch trap handling to use MMIO handler Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 13/22] hw/serial: Refactor trap handler Andre Przywara
2021-03-16 15:40 ` Alexandru Elisei
2021-03-15 15:33 ` [PATCH kvmtool v3 14/22] hw/serial: Switch to new trap handlers Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 15/22] vfio: Refactor ioport trap handler Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 16/22] vfio: Switch to new ioport trap handlers Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 17/22] virtio: Switch trap handling to use MMIO handler Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 18/22] pci: " Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 19/22] Remove ioport specific routines Andre Przywara
2021-03-15 15:33 ` [PATCH kvmtool v3 20/22] arm: Reorganise and document memory map Andre Przywara
2021-03-17 15:17 ` Alexandru Elisei
2021-03-15 15:33 ` [PATCH kvmtool v3 21/22] hw/serial: ARM/arm64: Use MMIO at higher addresses Andre Przywara
2021-03-17 16:17 ` Alexandru Elisei [this message]
2021-03-15 15:33 ` [PATCH kvmtool v3 22/22] hw/rtc: " Andre Przywara
2021-03-17 17:44 ` [PATCH kvmtool v3 00/22] Unify I/O port and MMIO trap handling Alexandru Elisei
2021-03-18 10:04 ` Will Deacon
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=7ce22c90-bf5c-b976-5698-85a7605bc1b7@arm.com \
--to=alexandru.elisei@arm.com \
--cc=andre.przywara@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;
as well as URLs for NNTP newsgroup(s).