From: Nicolin Chen <nicolinc@nvidia.com>
To: <will@kernel.org>, <robin.murphy@arm.com>, <jgg@nvidia.com>,
<kevin.tian@intel.com>
Cc: <joro@8bytes.org>, <linux-tegra@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <eric.auger@redhat.com>,
<skolothumtho@nvidia.com>
Subject: [PATCH 0/2] iommu/tegra241-cmdqv: Fix initialization and uAPI related to HYP_OWN
Date: Thu, 12 Mar 2026 17:36:33 -0700 [thread overview]
Message-ID: <cover.1773361875.git.nicolinc@nvidia.com> (raw)
Hi,
Eric and Shameer found a bug in kernel driver that supports_cmd is set in
an incorrect order related to the hyp_own finalization. This results in a
unnecessary command filter in the host environment that sends unsupported
(non-invalidation) commands to the SMMU CMDQ.
Also, Eric pointed it out that the requirement of VMM wiring HYP_OWN to 0
is unclear.
Thus, I am sending this small series to address these issues.
Nicolin Chen (2):
iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init()
iommu/tegra241-cmdqv: Update uAPI to clarify HYP_OWN requirement
include/uapi/linux/iommufd.h | 5 +++++
drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.c | 7 ++++---
2 files changed, 9 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-13 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 0:36 Nicolin Chen [this message]
2026-03-13 0:36 ` [PATCH 1/2] iommu/tegra241-cmdqv: Set supports_cmd op in tegra241_vcmdq_hw_init() Nicolin Chen
2026-03-13 9:37 ` Shameer Kolothum Thodi
2026-03-23 13:58 ` Eric Auger
2026-03-13 0:36 ` [PATCH 2/2] iommu/tegra241-cmdqv: Update uAPI to clarify HYP_OWN requirement Nicolin Chen
2026-03-19 14:47 ` Will Deacon
2026-03-23 13:12 ` Jason Gunthorpe
2026-03-23 14:03 ` Eric Auger
2026-03-24 15:08 ` [PATCH 0/2] iommu/tegra241-cmdqv: Fix initialization and uAPI related to HYP_OWN Will Deacon
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=cover.1773361875.git.nicolinc@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=skolothumtho@nvidia.com \
--cc=will@kernel.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