From: Eric Auger <eric.auger@redhat.com>
To: Shameer Kolothum <skolothumtho@nvidia.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, nicolinc@nvidia.com,
nathanc@nvidia.com, mochs@nvidia.com, jgg@nvidia.com,
jonathan.cameron@huawei.com, zhangfei.gao@linaro.org,
zhenzhong.duan@intel.com, kjaju@nvidia.com
Subject: Re: [PATCH v2 0/4] vEVENTQ support for accelerated SMMUv3 devices
Date: Tue, 9 Dec 2025 11:18:53 +0100 [thread overview]
Message-ID: <69e9ac12-596d-415a-a669-980ba67d22ba@redhat.com> (raw)
In-Reply-To: <20251204092245.5157-1-skolothumtho@nvidia.com>
On 12/4/25 10:22 AM, Shameer Kolothum wrote:
> Hi,
>
> Changes from RFC v1:
> https://lore.kernel.org/qemu-devel/20251105154657.37386-1-skolothumtho@nvidia.com/
>
> -Rebased on v6[0] of the "accelerated SMMUv3" series
> -Addressed feedback on the RFC. Thanks!
> -Dropped the RFC tag as the accelerated series is now more mature, and once
> that lands, it makes sense to pick this up as well since it enables the
> delivery of SMMUv3 events to the guest.
>
> When accel=on is enabled for an SMMUv3 instance, the host hardware SMMUv3
> may generate Stage-1 (S1) fault or event notifications that are intended
> for the vIOMMU instance in userspace.
>
> This series adds QEMU support for receiving such host events through the
> vEVENTQ interface and propagating them to the guest. The implementation
> uses the vEVENTQ support provided by the IOMMUFD subsystem in the kernel.
>
> I have lightly this on a Grace platform using some hacks to generate fault
tested
Eric
> events. Further testing and feedback are welcome.
>
> Thanks,
> Shameer
>
> [0]https://lore.kernel.org/qemu-devel/20251120132213.56581-1-skolothumtho@nvidia.com/
>
> Nicolin Chen (2):
> backends/iommufd: Introduce iommufd_backend_alloc_veventq
> hw/arm/smmuv3-accel: Allocate vEVENTQ for accelerated SMMUv3 devices
>
> Shameer Kolothum (2):
> hw/arm/smmuv3: Introduce a helper function for event propagation
> hw/arm/smmuv3-accel: Read and propagate host vIOMMU events
>
> backends/iommufd.c | 31 ++++++++++
> backends/trace-events | 1 +
> hw/arm/smmuv3-accel.c | 120 ++++++++++++++++++++++++++++++++++++++-
> hw/arm/smmuv3-accel.h | 8 +++
> hw/arm/smmuv3-internal.h | 4 ++
> hw/arm/smmuv3.c | 25 ++++++--
> hw/arm/trace-events | 2 +-
> include/system/iommufd.h | 12 ++++
> 8 files changed, 195 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2025-12-09 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 9:22 [PATCH v2 0/4] vEVENTQ support for accelerated SMMUv3 devices Shameer Kolothum
2025-12-04 9:22 ` [PATCH v2 1/4] backends/iommufd: Introduce iommufd_backend_alloc_veventq Shameer Kolothum
2025-12-09 10:31 ` Eric Auger
2025-12-10 15:13 ` Shameer Kolothum
2025-12-04 9:22 ` [PATCH v2 2/4] hw/arm/smmuv3-accel: Allocate vEVENTQ for accelerated SMMUv3 devices Shameer Kolothum
2025-12-09 16:08 ` Eric Auger
2025-12-10 15:46 ` Shameer Kolothum
2025-12-04 9:22 ` [PATCH v2 3/4] hw/arm/smmuv3: Introduce a helper function for event propagation Shameer Kolothum
2025-12-10 7:52 ` Eric Auger
2025-12-11 7:38 ` Nicolin Chen
2025-12-04 9:22 ` [PATCH v2 4/4] hw/arm/smmuv3-accel: Read and propagate host vIOMMU events Shameer Kolothum
2025-12-10 8:19 ` Eric Auger
2025-12-10 16:19 ` Shameer Kolothum
2025-12-09 10:18 ` Eric Auger [this message]
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=69e9ac12-596d-415a-a669-980ba67d22ba@redhat.com \
--to=eric.auger@redhat.com \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kjaju@nvidia.com \
--cc=mochs@nvidia.com \
--cc=nathanc@nvidia.com \
--cc=nicolinc@nvidia.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.com \
--cc=zhangfei.gao@linaro.org \
--cc=zhenzhong.duan@intel.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 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).