From: Ethan Chen via <qemu-riscv@nongnu.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: <qemu-devel@nongnu.org>, <pbonzini@redhat.com>,
<palmer@dabbelt.com>, <alistair.francis@wdc.com>,
<bmeng.cn@gmail.com>, <liwei1518@gmail.com>,
<dbarboza@ventanamicro.com>, <zhiwei_liu@linux.alibaba.com>,
<qemu-riscv@nongnu.org>
Subject: Re: [PATCH v7 1/2] hw/misc/riscv_iopmp: Add RISC-V IOPMP device
Date: Thu, 20 Jun 2024 10:30:06 +0800 [thread overview]
Message-ID: <ZnOULg2sd7YZHFQi@ethan84-VirtualBox> (raw)
In-Reply-To: <8def1779-6fc8-4e53-9542-20fe83651c0b@weilnetz.de>
On Mon, Jun 17, 2024 at 02:09:34PM +0200, Stefan Weil wrote:
> [EXTERNAL MAIL]
>
> Am 12.06.24 um 05:17 schrieb Ethan Chen via:
> > Support basic functions of IOPMP specification v0.9.1 rapid-k model.
> > The specification url:
> > https://github.com/riscv-non-isa/iopmp-spec/releases/tag/v0.9.1
> >
> > IOPMP check memory access from device is valid or not. This implementation uses
> > IOMMU to change address space that device access. There are three possible
> > results of an access: valid, blocked, and stalled(stall is not supported in this
> > patch).
> >
> > If an access is valid, target address space is downstream_as.
> > If an access is blocked, it will go to blocked_io_as. The operation of
> > blocked_io_as could be a bus error, or it can respond a success with fabricated
> > data depending on IOPMP ERR_CFG register value.
> >
> > Signed-off-by: Ethan Chen <ethan84@andestech.com>
> > ---
> > hw/misc/Kconfig | 3 +
> > hw/misc/meson.build | 1 +
> > hw/misc/riscv_iopmp.c | 1002 +++++++++++++++++++++++++++++++++
> > hw/misc/trace-events | 4 +
> > include/hw/misc/riscv_iopmp.h | 152 +++++
> > 5 files changed, 1162 insertions(+)
> > create mode 100644 hw/misc/riscv_iopmp.c
> > create mode 100644 include/hw/misc/riscv_iopmp.h
>
> Should both new files have SPDX license identifiers?
>
> Regards,
> Stefan W.
Thank you for the reminder, I will add them.
Thanks,
Ethan
WARNING: multiple messages have this Message-ID (diff)
From: Ethan Chen via <qemu-devel@nongnu.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: <qemu-devel@nongnu.org>, <pbonzini@redhat.com>,
<palmer@dabbelt.com>, <alistair.francis@wdc.com>,
<bmeng.cn@gmail.com>, <liwei1518@gmail.com>,
<dbarboza@ventanamicro.com>, <zhiwei_liu@linux.alibaba.com>,
<qemu-riscv@nongnu.org>
Subject: Re: [PATCH v7 1/2] hw/misc/riscv_iopmp: Add RISC-V IOPMP device
Date: Thu, 20 Jun 2024 10:30:06 +0800 [thread overview]
Message-ID: <ZnOULg2sd7YZHFQi@ethan84-VirtualBox> (raw)
In-Reply-To: <8def1779-6fc8-4e53-9542-20fe83651c0b@weilnetz.de>
On Mon, Jun 17, 2024 at 02:09:34PM +0200, Stefan Weil wrote:
> [EXTERNAL MAIL]
>
> Am 12.06.24 um 05:17 schrieb Ethan Chen via:
> > Support basic functions of IOPMP specification v0.9.1 rapid-k model.
> > The specification url:
> > https://github.com/riscv-non-isa/iopmp-spec/releases/tag/v0.9.1
> >
> > IOPMP check memory access from device is valid or not. This implementation uses
> > IOMMU to change address space that device access. There are three possible
> > results of an access: valid, blocked, and stalled(stall is not supported in this
> > patch).
> >
> > If an access is valid, target address space is downstream_as.
> > If an access is blocked, it will go to blocked_io_as. The operation of
> > blocked_io_as could be a bus error, or it can respond a success with fabricated
> > data depending on IOPMP ERR_CFG register value.
> >
> > Signed-off-by: Ethan Chen <ethan84@andestech.com>
> > ---
> > hw/misc/Kconfig | 3 +
> > hw/misc/meson.build | 1 +
> > hw/misc/riscv_iopmp.c | 1002 +++++++++++++++++++++++++++++++++
> > hw/misc/trace-events | 4 +
> > include/hw/misc/riscv_iopmp.h | 152 +++++
> > 5 files changed, 1162 insertions(+)
> > create mode 100644 hw/misc/riscv_iopmp.c
> > create mode 100644 include/hw/misc/riscv_iopmp.h
>
> Should both new files have SPDX license identifiers?
>
> Regards,
> Stefan W.
Thank you for the reminder, I will add them.
Thanks,
Ethan
next prev parent reply other threads:[~2024-06-20 2:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 3:17 [PATCH v7 0/2] Support RISC-V IOPMP Ethan Chen via
2024-06-12 3:17 ` Ethan Chen via
2024-06-12 3:17 ` [PATCH v7 1/2] hw/misc/riscv_iopmp: Add RISC-V IOPMP device Ethan Chen via
2024-06-12 3:17 ` Ethan Chen via
2024-06-13 9:26 ` LIU Zhiwei
2024-06-14 1:46 ` Ethan Chen via
2024-06-14 1:46 ` Ethan Chen via
2024-06-14 13:02 ` LIU Zhiwei
2024-06-17 11:28 ` LIU Zhiwei
2024-06-20 2:27 ` Ethan Chen via
2024-06-20 2:27 ` Ethan Chen via
2024-06-17 12:09 ` Stefan Weil via
2024-06-17 12:09 ` Stefan Weil via
2024-06-20 2:30 ` Ethan Chen via [this message]
2024-06-20 2:30 ` Ethan Chen via
2024-06-12 3:17 ` [PATCH v7 2/2] hw/riscv/virt: Add IOPMP support Ethan Chen via
2024-06-12 3:17 ` Ethan Chen via
2024-06-21 5:54 ` Alistair Francis
2024-06-24 1:46 ` Ethan Chen via
2024-06-24 1:46 ` Ethan Chen via
2024-06-26 1:22 ` Alistair Francis
2024-06-26 5:53 ` Ethan Chen via
2024-06-26 5:53 ` Ethan Chen via
2024-07-08 4:26 ` Alistair Francis
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=ZnOULg2sd7YZHFQi@ethan84-VirtualBox \
--to=qemu-riscv@nongnu.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=ethan84@andestech.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
--cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.