[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine
From: |
Joel Stanley |
Subject: |
Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine |
Date: |
Thu, 2 Jun 2022 11:42:30 +0000 |
Hi Stafford,
On Fri, 27 May 2022 at 17:27, Stafford Horne <shorne@gmail.com> wrote:
>
> This patch add the OpenRISC virtual machine 'virt' for OpenRISC. This
> platform allows for a convenient CI platform for toolchain, software
> ports and the OpenRISC linux kernel port.
>
> Much of this has been sourced from the m68k and riscv virt platforms.
It's a good idea! I did some playing around with your patch today.
I'd suggest adding something to docs/system/target-openrsic.rst,
including an example command lines.
>
> The platform provides:
> - OpenRISC SMP with up to 8 cpus
You have this:
#define VIRT_CPUS_MAX 4
I tried booting with -smp 4 and it locked up when starting userspace
(or I stopped getting serial output?):
[ 0.060000] smp: Brought up 1 node, 4 CPUs
...
[ 0.960000] Run /init as init process
Running with -smp 2 and 3 worked. It does make booting much much slower.
> - A virtio bus with up to 8 devices
How do we go about adding a virtio-net-device to this bus?
I tried this:
$ ./qemu-system-or1k -M virt -nographic -kernel
~/dev/kernels/shenki/or1ksim/vmlinux -initrd
~/dev/buildroot/openrisc/images/rootfs.cpio -device
virtio-net-device,netdev=net0 -netdev user,id=net0
I thought it wasn't working, but I just needed to enable the drivers,
and from there it worked:
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_MMIO=y
I also tested the virtio rng device which appeared to work.
# CONFIG_HW_RANDOM is not set
CONFIG_HW_RANDOM=y
CONFIG_HW_RANDOM_VIRTIO=y
> - Standard ns16550a serial
> - Goldfish RTC
-device virtio-rng-device,rng=rng0 -object rng-builtin,id=rng0
I enabled the options:
CONFIG_RTC_CLASS=y
# CONFIG_RTC_SYSTOHC is not set
# CONFIG_RTC_NVMEM is not set
CONFIG_RTC_DRV_GOLDFISH=y
But it didn't work. It seems the goldfish rtc model doesn't handle a
big endian guest running on my little endian host.
Doing this fixes it:
- .endianness = DEVICE_NATIVE_ENDIAN,
+ .endianness = DEVICE_HOST_ENDIAN,
[ 0.190000] goldfish_rtc 96005000.rtc: registered as rtc0
[ 0.190000] goldfish_rtc 96005000.rtc: setting system clock to
2022-06-02T11:16:04 UTC (1654168564)
But literally no other model in the tree does this, so I suspect it's
not the right fix.
> - SiFive TEST device for poweroff and reboot
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_SYSCON=y
CONFIG_POWER_RESET_SYSCON_POWEROFF=y
CONFIG_SYSCON_REBOOT_MODE=y
Adding the syscon/mfd cruft to the kernel adds about 43KB just for
rebooting. I guess that's okay as we're only dealing with a virtual
platform.
> - Generated RTC to automatically configure the guest kernel
Did you mean device tree?
>
> Signed-off-by: Stafford Horne <shorne@gmail.com>
> ---
> configs/devices/or1k-softmmu/default.mak | 1 +
> hw/openrisc/Kconfig | 9 +
> hw/openrisc/meson.build | 1 +
> hw/openrisc/virt.c | 429 +++++++++++++++++++++++
> 4 files changed, 440 insertions(+)
> create mode 100644 hw/openrisc/virt.c
>
> diff --git a/configs/devices/or1k-softmmu/default.mak
> b/configs/devices/or1k-softmmu/default.mak
> index 5b3ac89491..f3bf816067 100644
> --- a/configs/devices/or1k-softmmu/default.mak
> +++ b/configs/devices/or1k-softmmu/default.mak
> @@ -5,3 +5,4 @@ CONFIG_SEMIHOSTING=y
> # Boards:
> #
> CONFIG_OR1K_SIM=y
> +CONFIG_OR1K_VIRT=y
> diff --git a/hw/openrisc/Kconfig b/hw/openrisc/Kconfig
> index 8f284f3ba0..202134668e 100644
> --- a/hw/openrisc/Kconfig
> +++ b/hw/openrisc/Kconfig
> @@ -4,3 +4,12 @@ config OR1K_SIM
> select OPENCORES_ETH
> select OMPIC
> select SPLIT_IRQ
> +
> +config OR1K_VIRT
> + bool
> + imply VIRTIO_VGA
> + imply TEST_DEVICES
> + select GOLDFISH_RTC
> + select SERIAL
> + select SIFIVE_TEST
> + select VIRTIO_MMIO
You could include the liteeth device too if we merged that.
> diff --git a/hw/openrisc/virt.c b/hw/openrisc/virt.c
> new file mode 100644
> index 0000000000..147196fda3
> --- /dev/null
> +++ b/hw/openrisc/virt.c
> @@ -0,0 +1,429 @@
> +/*
> + * OpenRISC QEMU virtual machine.
> + *
> + * Copyright (c) 2022 Stafford Horne <shorne@gmail.com>
> + *
> + * This library is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU Lesser General Public
> + * License as published by the Free Software Foundation; either
> + * version 2.1 of the License, or (at your option) any later version.
> + *
> + * This library is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Lesser General Public License for more details.
> + *
> + * You should have received a copy of the GNU Lesser General Public
> + * License along with this library; if not, see
> <http://www.gnu.org/licenses/>.
I think you can use the SPDX tag here instead of writing out the text.
> +static void openrisc_virt_init(MachineState *machine)
> +{
> + ram_addr_t ram_size = machine->ram_size;
> + const char *kernel_filename = machine->kernel_filename;
> + OpenRISCCPU *cpus[VIRT_CPUS_MAX] = {};
> + OR1KVirtState *state = VIRT_MACHINE(machine);
> + MemoryRegion *ram;
> + hwaddr load_addr;
> + int n;
> + unsigned int smp_cpus = machine->smp.cpus;
> +
> + openrisc_virt_rtc_init(state, virt_memmap[VIRT_RTC].base,
> + virt_memmap[VIRT_RTC].size, smp_cpus, cpus,
> + VIRT_RTC_IRQ);
> +
> + for (n = 0; n < VIRTIO_COUNT; n++) {
This would make more sense to me if you constructed the IRQ and base
here, and then passed the actual base and irq number to your
_virtio_init:
size_t size = virt_memmap[VIRT_VIRTIO].size;
openrisc_virt_virtio_init(state, virt_memmap[VIRT_VIRTIO].base
+ size * n,
size, smp_cpus, cpus, VIRT_VIRTIO_IRQ + n);
> + openrisc_virt_virtio_init(state, virt_memmap[VIRT_VIRTIO].base,
> + virt_memmap[VIRT_VIRTIO].size,
> + smp_cpus, cpus, VIRT_VIRTIO_IRQ, n);
> + }
> +
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine,
Joel Stanley <=
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Richard Henderson, 2022/06/02
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Geert Uytterhoeven, 2022/06/02
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Stafford Horne, 2022/06/02
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Geert Uytterhoeven, 2022/06/03
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Stafford Horne, 2022/06/04
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Stafford Horne, 2022/06/05
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Jason A. Donenfeld, 2022/06/05
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Jason A. Donenfeld, 2022/06/07
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Geert Uytterhoeven, 2022/06/07
- Re: [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine, Arnd Bergmann, 2022/06/07