From: Jason Gunthorpe <jgg@nvidia.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
Will Deacon <will@kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>
Subject: Re: [PATCH] iommu/arm-smmu-v3: Improve uAPI comment for IOMMU_HW_INFO_TYPE_ARM_SMMUV3
Date: Fri, 15 Nov 2024 12:32:24 -0400 [thread overview]
Message-ID: <20241115163224.GZ35230@nvidia.com> (raw)
In-Reply-To: <BN9PR11MB527626CD708AAAC3473F7BF98C242@BN9PR11MB5276.namprd11.prod.outlook.com>
On Fri, Nov 15, 2024 at 08:27:12AM +0000, Tian, Kevin wrote:
> > - * a VMM is using this information to construct emulated copies of these
> > - * registers it should only forward bits that it knows it can support.
> > + * idr[0]: ST_LEVEL, TERM_MODEL, STALL_MODEL, TTENDIAN , CD2L,
> > ASID16, TTF
> > + * idr[1]: SIDSIZE, SSIDSIZE
> > + * idr[3]: BBML, RIL
> > + * idr[5]: VAX, GRAN64K, GRAN16K, GRAN4K
> > *
> > - * In future, presence of required kernel support will be indicated in flags.
>
> probably add a umbrella sentence to mark out following features not
> reported via IDRs
*
* The following bits in the vIDR should be obtained from other sources:
* - S1P should be assumed to be true if a NESTED HWPT can be created
>
> > + * - S1P should be assumed to be true if a NESTED HWPT can be created
> > + * - VFIO/iommufd only support platforms with COHACC, it should be
> > assumed to be
> > + * true.
> > + * - ATS is a per-device property. If the VMM describes any devices as ATS
> > + * capable in ACPI/DT it should set the corresponding idr.
> > + *
> > + * This list may expand in future (eg E0PD, AIE, PBHA, D128, DS etc). It is
> > + * important that VMMs do not read bits outside the list to allow for
> > + * compatibility with future kernels. Several features in the SMMUv3
> > + * architecture are not currently supported by the kernel for nesting: HTTU,
> > + * BTM, MPAM and others.
>
> Not sure why HTTU etc. are remarked separately instead of appending to
> the list of E0PD etc.
We know HTTU requires a kernel change, E0PD I think won't.
> there is a reason for kernel not reporting a certain feature now, no
> matter it's because the kernel hasn't supported it or supported it
> but just doesn't want to report. Knowing the difference doesn't help
> the business in VMM...
Right, it doesn't help the VMM, this is more guidance for future
people that might want to enable these things.
Thanks,
Jason
next prev parent reply other threads:[~2024-11-15 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 18:51 [PATCH] iommu/arm-smmu-v3: Improve uAPI comment for IOMMU_HW_INFO_TYPE_ARM_SMMUV3 Jason Gunthorpe
2024-11-15 8:27 ` Tian, Kevin
2024-11-15 16:32 ` Jason Gunthorpe [this message]
2024-12-03 17:31 ` 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=20241115163224.GZ35230@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=patches@lists.linux.dev \
--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