From: fangyu.yu@linux.alibaba.com
To: jgg@nvidia.com
Cc: alex@ghiti.fr, andrew.jones@linux.dev, anup@brainfault.org,
aou@eecs.berkeley.edu, atish.patra@linux.dev,
baolu.lu@linux.intel.com, fangyu.yu@linux.alibaba.com,
gong.shuai@sanechips.com.cn, guoren@kernel.org,
iommu@lists.linux.dev, jgg@ziepe.ca, joerg.roedel@amd.com,
joro@8bytes.org, jroedel@suse.de, kevin.tian@intel.com,
kvm-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
pjw@kernel.org, robin.murphy@arm.com, skhawaja@google.com,
tanchi25@mails.ucas.ac.cn, tomasz.jeznach@linux.dev,
vasant.hegde@amd.com, will@kernel.org, zong.li@sifive.com
Subject: Re: [RFC PATCH v5 07/10] iommu/riscv: Add domain_alloc_paging_flags for second-stage domain
Date: Thu, 29 Oct 2026 09:41:17 +0800 [thread overview]
Message-ID: <20261029014117.80953-1-fangyu.yu@linux.alibaba.com> (raw)
In-Reply-To: <179320128834.2412245.6365239689333877950.b4-review@b4>
>> [ ... 22 lines skipped ... ]
>> -static struct iommu_domain *riscv_iommu_alloc_paging_domain(struct device *dev)
>> +static struct iommu_domain *
>> +riscv_iommu_domain_alloc_paging_flags(struct device *dev, u32 flags,
>> + const struct iommu_user_data *user_data)
>> {
>> struct pt_iommu_riscv_64_cfg cfg = {};
>> struct riscv_iommu_domain *domain;
>> struct riscv_iommu_device *iommu;
>> int ret;
>> + const u32 supported_flags = IOMMU_HWPT_ALLOC_DIRTY_TRACKING |
>> + IOMMU_HWPT_ALLOC_NEST_PARENT;
>>
>> - iommu = dev_to_iommu(dev);
>> - if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV57) {
>> - cfg.common.hw_max_vasz_lg2 = 57;
>> - } else if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV48) {
>> - cfg.common.hw_max_vasz_lg2 = 48;
>> - } else if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV39) {
>> - cfg.common.hw_max_vasz_lg2 = 39;
>> - } else {
>> - dev_err(dev, "cannot find supported page table mode\n");
>> - return ERR_PTR(-ENODEV);
>> - }
>> - cfg.common.hw_max_oasz_lg2 = 56;
>> + if (flags & ~supported_flags)
>> + return ERR_PTR(-EOPNOTSUPP);
>
>This probably isn't needed since the switch checks it?
>
Right, the switch already enumerates all valid combinations, and
the default case returns -EOPNOTSUPP, so this check is
redundant. I'll drop it, along with supported_flags, in v6.
>> [ ... 30 lines skipped ... ]
>> + switch (flags) {
>> + case 0:
>> + cfg.common.features |= BIT(PT_FEAT_SIGN_EXTEND);
>> + if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV57) {
>> + cfg.common.hw_max_vasz_lg2 = 57;
>> + } else if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV48) {
>> + cfg.common.hw_max_vasz_lg2 = 48;
>> + } else if (iommu->caps & RISCV_IOMMU_CAPABILITIES_SV39) {
>> + cfg.common.hw_max_vasz_lg2 = 39;
>> + } else {
>> + ret = -ENODEV;
>> + goto err_free;
>> + }
>> + domain->pscid = ida_alloc_range(&riscv_iommu_pscids, 1,
>> + RISCV_IOMMU_MAX_PSCID, GFP_KERNEL);
>> + if (domain->pscid < 0) {
>> + ret = -ENOMEM;
>> + goto err_free;
>> + }
>> + break;
>
>I'd prefer you make functions riscv_iommu_init_domain_s1/s2() to put
>this in, it will be clearer
>
Agreed. In v6, I will move the page table mode selection, the
PSCID/GSCID allocation, and the stage-specific feature bits
into riscv_iommu_init_domain_s1/s2().
Thanks,
Fangyu
>It looks ok otherwise
>
>Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
>
>--
>Jason
next prev parent reply other threads:[~2026-10-29 1:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:40 [RFC PATCH v5 00/10] iommu/riscv: Add hardware dirty tracking for second-stage domains fangyu.yu
2026-10-20 9:40 ` [RFC PATCH v5 01/10] iommupt: Add RISC-V Second-stage (iohgatp) page table support fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:40 ` [RFC PATCH v5 02/10] iommupt: Add RISC-V dirty tracking PTE ops fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:40 ` [RFC PATCH v5 03/10] iommu/riscv: report iommu capabilities fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:41 ` [RFC PATCH v5 04/10] iommu/riscv: use data structure instead of individual values fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-20 9:41 ` [RFC PATCH v5 05/10] iommu/riscv: support GSCID and GVMA invalidation command fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 06/10] RISC-V: KVM: Enable KVM_VFIO interfaces on RISC-V arch fangyu.yu
2026-10-20 9:41 ` [RFC PATCH v5 07/10] iommu/riscv: Add domain_alloc_paging_flags for second-stage domain fangyu.yu
2026-10-28 15:28 ` Jason Gunthorpe
2026-10-29 1:41 ` fangyu.yu [this message]
2026-10-20 9:41 ` [RFC PATCH v5 08/10] iommu/riscv: Pre-enable GADE for second-stage domains fangyu.yu
2026-10-27 11:43 ` Nutty.Liu
2026-10-20 9:41 ` [RFC PATCH v5 09/10] iommu/riscv: Add dirty tracking support " fangyu.yu
2026-10-27 11:52 ` Nutty.Liu
2026-10-20 9:41 ` [RFC PATCH v5 10/10] iommu/riscv: Add IOTINVAL.GVMA invalidations fangyu.yu
2026-10-27 11:46 ` Nutty.Liu
2026-10-28 15:28 ` [RFC PATCH v5 00/10] iommu/riscv: Add hardware dirty tracking for second-stage domains Jason Gunthorpe
2026-10-29 1:52 ` fangyu.yu
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=20261029014117.80953-1-fangyu.yu@linux.alibaba.com \
--to=fangyu.yu@linux.alibaba.com \
--cc=alex@ghiti.fr \
--cc=andrew.jones@linux.dev \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=baolu.lu@linux.intel.com \
--cc=gong.shuai@sanechips.com.cn \
--cc=guoren@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kevin.tian@intel.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--cc=tanchi25@mails.ucas.ac.cn \
--cc=tomasz.jeznach@linux.dev \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=zong.li@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®