From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux IOMMU <iommu@lists.linux.dev>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Pranjal Shrivastava <praan@google.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] iommu/arm-smmu-v3-iommufd: Separate vDEVICE allocation list
Date: Wed, 26 Nov 2025 10:36:03 +0700 [thread overview]
Message-ID: <20251126033602.28871-2-bagasdotme@gmail.com> (raw)
Stephen Rothwell reports htmldocs warnings when merging iommufd tree:
Documentation/userspace-api/iommufd:335: include/uapi/linux/iommufd.h:456: ERROR: Unexpected indentation. [docutils]
Documentation/userspace-api/iommufd:335: include/uapi/linux/iommufd.h:457: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Fix them by separating vDEVICE allocation list from preceding paragraph.
Fixes: 9f0b286fe40130 ("iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20251126125920.207fc959@canb.auug.org.au/
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
include/uapi/linux/iommufd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/iommufd.h b/include/uapi/linux/iommufd.h
index 225671603ade66..2c41920b641dc1 100644
--- a/include/uapi/linux/iommufd.h
+++ b/include/uapi/linux/iommufd.h
@@ -453,6 +453,7 @@ struct iommu_hwpt_vtd_s1 {
*
* It's suggested to allocate a vDEVICE object carrying vSID and then re-attach
* the nested domain, as soon as the vSID is available in the VMM level:
+ *
* - when Cfg=translate, a vDEVICE must be allocated prior to attaching to the
* allocated nested domain, as CD/ATS invalidations and vevents need a vSID.
* - when Cfg=bypass/abort, a vDEVICE is not enforced during the nested domain
base-commit: 800b311b5afbca04e204eec98ee12667c88e9ae5
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-11-26 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 3:36 Bagas Sanjaya [this message]
2025-11-26 3:58 ` [PATCH] iommu/arm-smmu-v3-iommufd: Separate vDEVICE allocation list Nicolin Chen
2025-11-26 18:22 ` Jason Gunthorpe
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=20251126033602.28871-2-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praan@google.com \
--cc=sfr@canb.auug.org.au \
/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.