From: Nicolin Chen <nicolinc@nvidia.com>
To: Pranjal Shrivastava <praan@google.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Kevin Tian <kevin.tian@intel.com>,
"Will Deacon" <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Peter Shier <pshier@google.com>,
<iommu@lists.linux.dev>
Subject: Re: [PATCH v3] iommu: Clarify uAPI errno for unsupported data types
Date: Thu, 19 Nov 2026 11:54:33 -0800 [thread overview]
Message-ID: <av9T+V268uF447sN@nvidia.com> (raw)
In-Reply-To: <20261119192355.2428207-1-praan@google.com>
On Thu, Nov 19, 2026 at 07:23:55PM +0000, Pranjal Shrivastava wrote:
> The IOMMU_HWPT_INVALIDATE uAPI says that an empty request array "can be
> used to check if the given @data_type is supported or not by kernel",
> but not what to look for. And the iommu_copy_struct_*() helpers and the
> Intel VT-d, ARM SMMUv3 and selftest invalidation ops reject unsupported
> data types with -EINVAL, which means that the request was understood but
> a field is not correct.
>
> Return -EOPNOTSUPP for an unsupported data type instead and document it
> as what the probe looks for. Since arm_vsmmu_alloc_domain_nested() uses
> the copy helper, it now returns -EOPNOTSUPP, like the other nested
> domain allocators. Update and extend the selftests accordingly.
>
> Signed-off-by: Pranjal Shrivastava <praan@google.com>
Acked-by: Nicolin Chen <nicolinc@nvidia.com>
prev parent reply other threads:[~2026-11-19 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 19:23 [PATCH v3] iommu: Clarify uAPI errno for unsupported data types Pranjal Shrivastava
2026-11-19 19:54 ` Nicolin Chen [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=av9T+V268uF447sN@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=praan@google.com \
--cc=pshier@google.com \
--cc=robin.murphy@arm.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 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.