From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: jgg@nvidia.com, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, will@kernel.org, joro@8bytes.org,
kevin.tian@intel.com, jsnitsel@redhat.com, vasant.hegde@amd.com,
iommu@lists.linux.dev, santosh.shukla@amd.com,
sairaj.arunkodilkar@amd.com, jon.grimm@amd.com,
prashanthpra@google.com, wvw@google.com, wnliu@google.com,
gptran@google.com, kpsingh@google.com
Subject: Re: [PATCH 8/8] iommu/amd: Add support for nested domain attach/detach
Date: Wed, 27 Aug 2025 19:36:54 -0500 [thread overview]
Message-ID: <5a0fcde1-d746-4663-bb9b-4eeb3c9036c4@amd.com> (raw)
In-Reply-To: <aKjRB5MqCrJ2Px7G@Asurada-Nvidia>
On 8/22/2025 3:20 PM, Nicolin Chen wrote:
> On Wed, Aug 20, 2025 at 11:30:09AM +0000, Suravee Suthikulpanit wrote:
>> +static inline bool has_gcr3_table(struct gcr3_tbl_info *gcr3_info)
>> +{
>> + if (!gcr3_info || (!gcr3_info->gcr3_tbl && !gcr3_info->trp_gpa))
>> + return false;
>
> "gcr3_info" seems always pointing to "&dev_data->gcr3_info", which
> can never be NULL.
right
>> @@ -2061,7 +2087,14 @@ static void set_dte_entry(struct amd_iommu *iommu,
>> struct gcr3_tbl_info *gcr3_info = &dev_data->gcr3_info;
>> struct dev_table_entry *dte = &get_dev_table(iommu)[dev_data->devid];
>>
>> - if (gcr3_info && gcr3_info->gcr3_tbl)
>> + /*
>> + * For nested domain, use parent domain to setup v1 table
>> + * information and domain id.
>> + */
>> + if (amd_iommu_domain_is_nested(domain))
>> + domain = domain->parent;
>> +
>> + if (has_gcr3_table(gcr3_info))
>> domid = dev_data->gcr3_info.domid;
>
> There is already a local variable "gcr3_info".
right.
>> +static int nested_gcr3_update(struct protection_domain *pdom, struct device *dev)
>> +{
>> + struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
>> + struct iommu_hwpt_amd_v2 *hwpt = &pdom->guest_hwpt;
>> + struct pci_dev *pdev = to_pci_dev(dev);
>> +
>> + if (!pdev || !hwpt)
>> + return -EINVAL;
>
> to_pci_dev is a container_of from the dev. !pdev indicates a !dev
> that should never happen in the path of an attach_dev op. Or, did
> you actually want to check if dev_is_pci(dev)?
correct, I should have just checked for dev_is_pci(dev).
> Also, hwpt is "&pdom->guest_hwpt", which would never be NULL.
>
>> +static int amd_iommu_nested_attach_device(struct iommu_domain *dom, struct device *dev)
>> +{
>> + struct iommu_dev_data *dev_data = dev_iommu_priv_get(dev);
>> + struct protection_domain *pdom = to_pdomain(dom);
>> + struct pci_dev *pdev;
>> + int ret;
>> +
>> + if (dev_data->domain == pdom)
>> + return 0;
>> +
>> + ret = nested_gcr3_update(pdom, dev);
>> + if (ret)
>> + return ret;
>> +
>> + if (dev_data->domain)
>> + amd_iommu_detach_device(dev);
>> +
>> + ret = __amd_iommu_attach_device(dev, pdom);
>> + if (ret)
>> + return ret;
>> +
>> + pdev = dev_is_pci(dev_data->dev) ? to_pci_dev(dev_data->dev) : NULL;
>> + if (pdev)
>> + amd_iommu_pdev_enable_cap_ats(pdev);
>
> Is "dev_data->dev" expected to be "dev"?
correct.
Thanks for the review. I'll clean up the logic in
amd_iommu_nested_attach_device() to return error early for non-pci device.
Thanks,
Suravee
next prev parent reply other threads:[~2025-08-28 0:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 11:30 [PATCH 0/8] iommu/amd: Introduce Nested Translation support Suravee Suthikulpanit
2025-08-20 11:30 ` [PATCH 1/8] iommu/amd: Make amd_iommu_pdom_id_alloc() non-static Suravee Suthikulpanit
2025-09-02 13:03 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 2/8] iommu/amd: Making device attach / detach helpers non-static Suravee Suthikulpanit
2025-09-02 13:10 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 3/8] iommu/amd: Making amd_iommu_pdev_enable_cap_ats non-static Suravee Suthikulpanit
2025-08-20 11:30 ` [PATCH 4/8] iommu/amd: Introduce struct gcr3_tbl_info.giov Suravee Suthikulpanit
2025-09-02 13:07 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 5/8] iommufd: Introduce data struct for AMD nested domain allocation Suravee Suthikulpanit
2025-09-02 13:09 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 6/8] iommu/amd: Add support for nest parent " Suravee Suthikulpanit
2025-09-02 13:12 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 7/8] iommu/amd: Add support for nested " Suravee Suthikulpanit
2025-08-22 5:39 ` kernel test robot
2025-08-22 19:51 ` Nicolin Chen
2025-08-22 21:16 ` Jason Gunthorpe
2025-08-22 21:45 ` Nicolin Chen
2025-08-25 13:38 ` Jason Gunthorpe
2025-09-01 7:09 ` Sairaj Kodilkar
2025-09-02 11:42 ` Jason Gunthorpe
2025-09-02 13:18 ` Jason Gunthorpe
2025-08-20 11:30 ` [PATCH 8/8] iommu/amd: Add support for nested domain attach/detach Suravee Suthikulpanit
2025-08-22 20:20 ` Nicolin Chen
2025-08-28 0:36 ` Suthikulpanit, Suravee [this message]
2025-09-02 13:25 ` Jason Gunthorpe
2025-09-03 8:27 ` Sairaj Kodilkar
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=5a0fcde1-d746-4663-bb9b-4eeb3c9036c4@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=gptran@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kpsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=prashanthpra@google.com \
--cc=robin.murphy@arm.com \
--cc=sairaj.arunkodilkar@amd.com \
--cc=santosh.shukla@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=wnliu@google.com \
--cc=wvw@google.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®