From: Jonathan Cameron via <qemu-arm@nongnu.org>
To: Shameer Kolothum <skolothumtho@nvidia.com>
Cc: <qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
<eric.auger@redhat.com>, <peter.maydell@linaro.org>,
<nicolinc@nvidia.com>, <nathanc@nvidia.com>, <mochs@nvidia.com>,
<jan@nvidia.com>, <jgg@nvidia.com>, <zhangfei.gao@linaro.org>,
<zhenzhong.duan@intel.com>, <kjaju@nvidia.com>
Subject: Re: [PATCH v6 3/5] hw/arm/smmuv3-accel: Allocate vEVENTQ for accelerated SMMUv3 devices
Date: Mon, 16 Feb 2026 16:16:49 +0000 [thread overview]
Message-ID: <20260216161649.00005f3a@huawei.com> (raw)
In-Reply-To: <20260213103942.142823-4-skolothumtho@nvidia.com>
On Fri, 13 Feb 2026 10:39:40 +0000
Shameer Kolothum <skolothumtho@nvidia.com> wrote:
> From: Nicolin Chen <nicolinc@nvidia.com>
>
> When the guest enables the Event Queue and a vIOMMU is present, allocate a
> vEVENTQ object so that host-side events related to the vIOMMU can be
> received and propagated back to the guest.
>
> For cold-plugged devices using SMMUv3 acceleration, the vIOMMU is created
> before the guest boots. In this case, the vEVENTQ is allocated when the
> guest writes to SMMU_CR0 and sets EVENTQEN = 1.
>
> If no cold-plugged device exists at boot (i.e. no vIOMMU initially), the
> vEVENTQ is allocated when a vIOMMU is created, i.e. during the first
> device hot-plug.
>
> Also, rename the local error variable and refactor smmu_writel() to use
> a single error accumulator with error_propagate().
Why not split the rename out as a separate patch? I don't hugely mind just
feels like some noise in here could have been broken out before the real
change and made it a tiny bit easier to review.
I wouldn't bother unless you are respinning again for other reasons though!
J
>
> Event read and propagation will be added in a later patch.
>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
> Signed-off-by: Shameer Kolothum <skolothumtho@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: Shameer Kolothum <skolothumtho@nvidia.com>
Cc: <qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
<eric.auger@redhat.com>, <peter.maydell@linaro.org>,
<nicolinc@nvidia.com>, <nathanc@nvidia.com>, <mochs@nvidia.com>,
<jan@nvidia.com>, <jgg@nvidia.com>, <zhangfei.gao@linaro.org>,
<zhenzhong.duan@intel.com>, <kjaju@nvidia.com>
Subject: Re: [PATCH v6 3/5] hw/arm/smmuv3-accel: Allocate vEVENTQ for accelerated SMMUv3 devices
Date: Mon, 16 Feb 2026 16:16:49 +0000 [thread overview]
Message-ID: <20260216161649.00005f3a@huawei.com> (raw)
In-Reply-To: <20260213103942.142823-4-skolothumtho@nvidia.com>
On Fri, 13 Feb 2026 10:39:40 +0000
Shameer Kolothum <skolothumtho@nvidia.com> wrote:
> From: Nicolin Chen <nicolinc@nvidia.com>
>
> When the guest enables the Event Queue and a vIOMMU is present, allocate a
> vEVENTQ object so that host-side events related to the vIOMMU can be
> received and propagated back to the guest.
>
> For cold-plugged devices using SMMUv3 acceleration, the vIOMMU is created
> before the guest boots. In this case, the vEVENTQ is allocated when the
> guest writes to SMMU_CR0 and sets EVENTQEN = 1.
>
> If no cold-plugged device exists at boot (i.e. no vIOMMU initially), the
> vEVENTQ is allocated when a vIOMMU is created, i.e. during the first
> device hot-plug.
>
> Also, rename the local error variable and refactor smmu_writel() to use
> a single error accumulator with error_propagate().
Why not split the rename out as a separate patch? I don't hugely mind just
feels like some noise in here could have been broken out before the real
change and made it a tiny bit easier to review.
I wouldn't bother unless you are respinning again for other reasons though!
J
>
> Event read and propagation will be added in a later patch.
>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
> Signed-off-by: Shameer Kolothum <skolothumtho@nvidia.com>
next prev parent reply other threads:[~2026-02-16 16:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 10:39 [PATCH v6 0/5] vEVENTQ support for accelerated SMMUv3 devices Shameer Kolothum
2026-02-13 10:39 ` [PATCH v6 1/5] backends/iommufd: Introduce iommufd_backend_alloc_veventq Shameer Kolothum
2026-02-13 22:19 ` Nicolin Chen
2026-02-13 10:39 ` [PATCH v6 2/5] hw/arm/smmuv3-accel: Add viommu free helper Shameer Kolothum
2026-02-13 10:39 ` [PATCH v6 3/5] hw/arm/smmuv3-accel: Allocate vEVENTQ for accelerated SMMUv3 devices Shameer Kolothum
2026-02-13 22:19 ` Nicolin Chen
2026-02-16 8:58 ` Shameer Kolothum Thodi
2026-02-16 16:57 ` Peter Maydell
2026-02-16 17:28 ` Shameer Kolothum Thodi
2026-02-16 16:16 ` Jonathan Cameron via [this message]
2026-02-16 16:16 ` Jonathan Cameron via qemu development
2026-02-13 10:39 ` [PATCH v6 4/5] hw/arm/smmuv3: Introduce a helper function for event propagation Shameer Kolothum
2026-02-16 16:30 ` Jonathan Cameron via
2026-02-16 16:30 ` Jonathan Cameron via qemu development
2026-02-16 17:52 ` Shameer Kolothum Thodi
2026-02-13 10:39 ` [PATCH v6 5/5] hw/arm/smmuv3-accel: Read and propagate host vIOMMU events Shameer Kolothum
2026-02-13 22:29 ` Nicolin Chen
2026-02-13 22:31 ` [PATCH v6 0/5] vEVENTQ support for accelerated SMMUv3 devices Nicolin Chen
2026-02-16 9:13 ` Shameer Kolothum Thodi
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=20260216161649.00005f3a@huawei.com \
--to=qemu-arm@nongnu.org \
--cc=eric.auger@redhat.com \
--cc=jan@nvidia.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-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 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.