From: Alistair Francis <alistair23@gmail.com>
To: Ethan Chen <ethan84@andestech.com>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
edgar.iglesias@gmail.com, richard.henderson@linaro.org,
pbonzini@redhat.com, palmer@dabbelt.com,
alistair.francis@wdc.com, in.meng@windriver.com,
liweiwei@iscas.ac.cn, dbarboza@ventanamicro.com,
hiwei_liu@linux.alibaba.com, qemu-riscv@nongnu.org,
peterx@redhat.com, david@redhat.com
Subject: Re: [PATCH v4 4/4] hw/riscv/virt: Add IOPMP support
Date: Mon, 18 Dec 2023 14:16:07 +1000 [thread overview]
Message-ID: <CAKmqyKNOd5vi_QPsibmvmqBA_Z=3TSbPPyv9MxVk++g+ekiVNg@mail.gmail.com> (raw)
In-Reply-To: <20231122053251.440723-5-ethan84@andestech.com>
On Wed, Nov 22, 2023 at 3:36 PM Ethan Chen via <qemu-devel@nongnu.org> wrote:
>
> If a source device is connected to the IOPMP device, its memory access will be
> checked by the IOPMP rule.
>
> - Add 'iopmp=on' option to add an iopmp device and a dma device which is
> connected to the iopmp to machine. This option is assumed to be "off"
> - Add 'iopmp_cascade=on' option to add second iopmp device which is cascaded by
> first iopmp device to machine. When iopmp option is "off", this option has no
> effect.
>
> Signed-off-by: Ethan Chen <ethan84@andestech.com>
> ---
> docs/system/riscv/virt.rst | 11 +++++++
> hw/riscv/Kconfig | 2 ++
> hw/riscv/virt.c | 65 ++++++++++++++++++++++++++++++++++++++
> include/hw/riscv/virt.h | 10 +++++-
> 4 files changed, 87 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/riscv/virt.rst b/docs/system/riscv/virt.rst
> index f5fa7b8b29..e1b4aa4f94 100644
> --- a/docs/system/riscv/virt.rst
> +++ b/docs/system/riscv/virt.rst
> @@ -111,6 +111,17 @@ The following machine-specific options are supported:
> having AIA IMSIC (i.e. "aia=aplic-imsic" selected). When not specified,
> the default number of per-HART VS-level AIA IMSIC pages is 0.
>
> +- iopmp=[on|off]
> +
> + When this option is "on". An iopmp device and a dma device which is connected
> + to the iopmp are added to machine. This option is assumed to be "off".
> +
> +- iopmp_cascade=[on|off]
> +
> + When this option is "on". Second iopmp device which is cascaded by first iopmp
> + device is added to machine. When iopmp option is "off", this option has no
> + effect. This option is assumed to be "off".
> +
> Running Linux kernel
> --------------------
>
> diff --git a/hw/riscv/Kconfig b/hw/riscv/Kconfig
> index b6a5eb4452..c30a104aa4 100644
> --- a/hw/riscv/Kconfig
> +++ b/hw/riscv/Kconfig
> @@ -45,6 +45,8 @@ config RISCV_VIRT
> select FW_CFG_DMA
> select PLATFORM_BUS
> select ACPI
> + select ATCDMAC300
> + select RISCV_IOPMP
>
> config SHAKTI_C
> bool
> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
> index c7fc97e273..92b748bfc7 100644
> --- a/hw/riscv/virt.c
> +++ b/hw/riscv/virt.c
> @@ -53,6 +53,8 @@
> #include "hw/display/ramfb.h"
> #include "hw/acpi/aml-build.h"
> #include "qapi/qapi-visit-common.h"
> +#include "hw/misc/riscv_iopmp.h"
> +#include "hw/dma/atcdmac300.h"
>
> /*
> * The virt machine physical address space used by some of the devices
> @@ -97,6 +99,9 @@ static const MemMapEntry virt_memmap[] = {
> [VIRT_UART0] = { 0x10000000, 0x100 },
> [VIRT_VIRTIO] = { 0x10001000, 0x1000 },
> [VIRT_FW_CFG] = { 0x10100000, 0x18 },
> + [VIRT_IOPMP] = { 0x10200000, 0x100000 },
> + [VIRT_IOPMP2] = { 0x10300000, 0x100000 },
> + [VIRT_DMAC] = { 0x10400000, 0x100000 },
> [VIRT_FLASH] = { 0x20000000, 0x4000000 },
> [VIRT_IMSIC_M] = { 0x24000000, VIRT_IMSIC_MAX_SIZE },
> [VIRT_IMSIC_S] = { 0x28000000, VIRT_IMSIC_MAX_SIZE },
> @@ -1534,6 +1539,23 @@ static void virt_machine_init(MachineState *machine)
> sysbus_create_simple("goldfish_rtc", memmap[VIRT_RTC].base,
> qdev_get_gpio_in(mmio_irqchip, RTC_IRQ));
>
> + if (s->have_iopmp) {
> + /* IOPMP */
> + DeviceState *iopmp_dev = iopmp_create(memmap[VIRT_IOPMP].base,
> + qdev_get_gpio_in(DEVICE(mmio_irqchip), IOPMP_IRQ));
> + /* DMA with IOPMP */
> + DeviceState *dmac_dev = atcdmac300_create("atcdmac300",
> + memmap[VIRT_DMAC].base, memmap[VIRT_DMAC].size,
> + qdev_get_gpio_in(DEVICE(mmio_irqchip), DMAC_IRQ));
This isn't adding a RISC-V IOPMP, it's adding an Andes IOPMP. I don't
think we want to pull a specific vendor implementation into the virt
machine.
Alistair
> + atcdmac300_connect_iopmp(dmac_dev, &(IOPMP(iopmp_dev)->iopmp_as),
> + (StreamSink *)&(IOPMP(iopmp_dev)->transaction_info_sink), 0);
> + if (s->have_iopmp_cascade) {
> + DeviceState *iopmp_dev2 = iopmp_create(memmap[VIRT_IOPMP2].base,
> + qdev_get_gpio_in(DEVICE(mmio_irqchip), IOPMP2_IRQ));
> + cascade_iopmp(iopmp_dev, iopmp_dev2);
> + }
> + }
> +
> for (i = 0; i < ARRAY_SIZE(s->flash); i++) {
> /* Map legacy -drive if=pflash to machine properties */
> pflash_cfi01_legacy_drive(s->flash[i],
> @@ -1628,6 +1650,35 @@ static void virt_set_aclint(Object *obj, bool value, Error **errp)
> s->have_aclint = value;
> }
>
> +static bool virt_get_iopmp(Object *obj, Error **errp)
> +{
> + RISCVVirtState *s = RISCV_VIRT_MACHINE(obj);
> +
> + return s->have_iopmp;
> +}
> +
> +static void virt_set_iopmp(Object *obj, bool value, Error **errp)
> +{
> + RISCVVirtState *s = RISCV_VIRT_MACHINE(obj);
> +
> + s->have_iopmp = value;
> +}
> +
> +static bool virt_get_iopmp_cascade(Object *obj, Error **errp)
> +{
> + RISCVVirtState *s = RISCV_VIRT_MACHINE(obj);
> +
> + return s->have_iopmp_cascade;
> +}
> +
> +static void virt_set_iopmp_cascade(Object *obj, bool value, Error **errp)
> +{
> + RISCVVirtState *s = RISCV_VIRT_MACHINE(obj);
> +
> + s->have_iopmp_cascade = value;
> +}
> +
> +
> bool virt_is_acpi_enabled(RISCVVirtState *s)
> {
> return s->acpi != ON_OFF_AUTO_OFF;
> @@ -1730,6 +1781,20 @@ static void virt_machine_class_init(ObjectClass *oc, void *data)
> NULL, NULL);
> object_class_property_set_description(oc, "acpi",
> "Enable ACPI");
> +
> + object_class_property_add_bool(oc, "iopmp", virt_get_iopmp,
> + virt_set_iopmp);
> + object_class_property_set_description(oc, "iopmp",
> + "Set on/off to enable/disable "
> + "iopmp device");
> +
> + object_class_property_add_bool(oc, "iopmp-cascade",
> + virt_get_iopmp_cascade,
> + virt_set_iopmp_cascade);
> + object_class_property_set_description(oc, "iopmp-cascade",
> + "Set on/off to enable/disable "
> + "iopmp2 device which is cascaded by "
> + "iopmp1 device");
> }
>
> static const TypeInfo virt_machine_typeinfo = {
> diff --git a/include/hw/riscv/virt.h b/include/hw/riscv/virt.h
> index e5c474b26e..5fa2944d29 100644
> --- a/include/hw/riscv/virt.h
> +++ b/include/hw/riscv/virt.h
> @@ -54,6 +54,8 @@ struct RISCVVirtState {
>
> int fdt_size;
> bool have_aclint;
> + bool have_iopmp;
> + bool have_iopmp_cascade;
> RISCVVirtAIAType aia_type;
> int aia_guests;
> char *oem_id;
> @@ -82,12 +84,18 @@ enum {
> VIRT_PCIE_MMIO,
> VIRT_PCIE_PIO,
> VIRT_PLATFORM_BUS,
> - VIRT_PCIE_ECAM
> + VIRT_PCIE_ECAM,
> + VIRT_IOPMP,
> + VIRT_IOPMP2,
> + VIRT_DMAC,
> };
>
> enum {
> UART0_IRQ = 10,
> RTC_IRQ = 11,
> + DMAC_IRQ = 12,
> + IOPMP_IRQ = 13,
> + IOPMP2_IRQ = 14,
> VIRTIO_IRQ = 1, /* 1 to 8 */
> VIRTIO_COUNT = 8,
> PCIE_IRQ = 0x20, /* 32 to 35 */
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-12-18 4:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 5:32 [PATCH v4 0/4] Support RISC-V IOPMP Ethan Chen via
2023-11-22 5:32 ` [PATCH v4 1/4] hw/core: Add config stream Ethan Chen via
2023-12-18 4:02 ` Alistair Francis
2023-11-22 5:32 ` [PATCH v4 2/4] Add RISC-V IOPMP support Ethan Chen via
2023-12-18 4:04 ` Alistair Francis
2023-12-27 2:26 ` Ethan Chen via
2023-11-22 5:32 ` [PATCH v4 3/4] hw/dma: Add Andes ATCDMAC300 support Ethan Chen via
2023-12-18 4:14 ` Alistair Francis
2023-11-22 5:32 ` [PATCH v4 4/4] hw/riscv/virt: Add IOPMP support Ethan Chen via
2023-12-18 4:16 ` Alistair Francis [this message]
2023-12-05 7:47 ` [PATCH v4 0/4] Support RISC-V IOPMP Ethan Chen via
2023-12-13 5:35 ` Ethan Chen via
2023-12-18 4:18 ` Alistair Francis
2023-12-21 6:38 ` Ethan Chen via
2024-01-22 6:01 ` Alistair Francis
2024-01-23 3:31 ` Ethan Chen via
2024-01-04 2:38 ` Ethan Chen via
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='CAKmqyKNOd5vi_QPsibmvmqBA_Z=3TSbPPyv9MxVk++g+ekiVNg@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=david@redhat.com \
--cc=dbarboza@ventanamicro.com \
--cc=edgar.iglesias@gmail.com \
--cc=ethan84@andestech.com \
--cc=hiwei_liu@linux.alibaba.com \
--cc=in.meng@windriver.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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).