From: Nicolin Chen <nicolinc@nvidia.com>
To: Shameer Kolothum <skolothumtho@nvidia.com>
Cc: <qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
<eric.auger@redhat.com>, <peter.maydell@linaro.org>,
<nathanc@nvidia.com>, <mochs@nvidia.com>, <jan@nvidia.com>,
<jgg@nvidia.com>, <jonathan.cameron@huawei.com>,
<zhangfei.gao@linaro.org>, <zhenzhong.duan@intel.com>,
<kjaju@nvidia.com>
Subject: Re: [PATCH v6 5/5] hw/arm/smmuv3-accel: Read and propagate host vIOMMU events
Date: Fri, 13 Feb 2026 14:29:40 -0800 [thread overview]
Message-ID: <aY+l1Pp87TkiqNeL@nvidia.com> (raw)
In-Reply-To: <20260213103942.142823-6-skolothumtho@nvidia.com>
On Fri, Feb 13, 2026 at 10:39:42AM +0000, Shameer Kolothum wrote:
> typedef struct SMMUv3AccelState {
> IOMMUFDViommu *viommu;
> IOMMUFDVeventq *veventq;
> + uint32_t last_event_seq;
> + bool event_start;
I see tegra241-cmdqv having these two as well. It seems they are
required by all veventq users. So, let's move these two into the
common IOMMUFDVeventq?
Otherwise,
Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
next prev parent reply other threads:[~2026-02-13 22:30 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
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 [this message]
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=aY+l1Pp87TkiqNeL@nvidia.com \
--to=nicolinc@nvidia.com \
--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=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 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.