From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org, wei.huang2@amd.com,
jsnitsel@redhat.com
Subject: Re: [PATCH 01/11] iommu/amd: Rename helper function rlookup_amd_iommu()
Date: Thu, 10 Aug 2023 16:06:52 -0700 [thread overview]
Message-ID: <bcd2749c-d4de-fa8c-c865-ac9ed184ea17@amd.com> (raw)
In-Reply-To: <ZNJfLQTJhOgorIHB@ziepe.ca>
On 8/8/2023 8:28 AM, Jason Gunthorpe wrote:
> On Tue, Aug 08, 2023 at 10:02:22AM +0000, Vasant Hegde wrote:
>> From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>>
>> Rename and make it available to other code.
>>
>> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>> Signed-off-by: Vasant Hegde <vasant.hegde@amd.com>
>> ---
>> drivers/iommu/amd/amd_iommu.h | 1 +
>> drivers/iommu/amd/iommu.c | 30 +++++++++++++++---------------
>> 2 files changed, 16 insertions(+), 15 deletions(-)
>>
>> diff --git a/drivers/iommu/amd/amd_iommu.h b/drivers/iommu/amd/amd_iommu.h
>> index 56996dc2868d..1471ab2dddd1 100644
>> --- a/drivers/iommu/amd/amd_iommu.h
>> +++ b/drivers/iommu/amd/amd_iommu.h
>> @@ -24,6 +24,7 @@ int amd_iommu_init_devices(void);
>> void amd_iommu_uninit_devices(void);
>> void amd_iommu_init_notifier(void);
>> void amd_iommu_set_rlookup_table(struct amd_iommu *iommu, u16 devid);
>> +struct amd_iommu *amd_iommu_rlookup_iommu(struct device *dev);
>>
>> #ifdef CONFIG_AMD_IOMMU_DEBUGFS
>> void amd_iommu_debugfs_setup(struct amd_iommu *iommu);
>> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
>> index 26e509ffe77a..77b913211c35 100644
>> --- a/drivers/iommu/amd/iommu.c
>> +++ b/drivers/iommu/amd/iommu.c
>> @@ -164,7 +164,7 @@ static struct amd_iommu *__rlookup_amd_iommu(u16 seg, u16 devid)
>> return NULL;
>> }
>>
>> -static struct amd_iommu *rlookup_amd_iommu(struct device *dev)
>> +struct amd_iommu *amd_iommu_rlookup_iommu(struct device *dev)
>> {
>
> Er, wah? This is a really confused function. It should just be:
>
> static inline struct amd_iommu *amd_device_to_iommu(struct device *dev)
> {
> return container_of(dev->iommu->iommu_dev, struct amd_iommu, iommu);
> }
>
> Right? At least for many of the call sites.
>
> The core code maintains the association of the iommu_device with each
> probe'd device automatically. The drivers don't need tables and
> searching.
The rlookup table is setup from the information in the IVRS table, which
contains list of devices belong to an IOMMU instance. This information
is used to for setting dev->iommu during probing (See
drivers/iommu/amd/iommu.c: amd_iommu_probe_device()).
Subsequently, it should be able to use the amd_device_to_iommu() you
provided as long as the device has not been released.
So, we can add the helper function above, and make sure to check that
dev->iommu is not NULL before calling the container_of().
Thanks,
Suravee
next prev parent reply other threads:[~2023-08-10 23:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 10:02 [PATCH 00/11] iommu/amd: SVA support (part 2) - refactor support for GCR3 table Vasant Hegde
2023-08-08 10:02 ` [PATCH 01/11] iommu/amd: Rename helper function rlookup_amd_iommu() Vasant Hegde
2023-08-08 15:28 ` Jason Gunthorpe
2023-08-10 23:06 ` Suthikulpanit, Suravee [this message]
2023-08-11 13:06 ` Jason Gunthorpe
2023-08-08 10:02 ` [PATCH 02/11] iommu/amd: Introduce struct protection_domain.pd_mode Vasant Hegde
2023-08-08 15:30 ` Jason Gunthorpe
2023-08-11 10:04 ` Vasant Hegde
2023-08-11 13:21 ` Jason Gunthorpe
2023-08-08 10:02 ` [PATCH 03/11] iommu/amd: Introduce per-device GCR3 table Vasant Hegde
2023-08-08 15:32 ` Jason Gunthorpe
2023-08-10 23:31 ` Suthikulpanit, Suravee
2023-08-08 10:02 ` [PATCH 04/11] iommu/amd: Use protection_domain.flags to check page table mode Vasant Hegde
2023-08-08 15:35 ` Jason Gunthorpe
2023-08-11 10:10 ` Vasant Hegde
2023-08-08 10:02 ` [PATCH 05/11] iommu/amd: Refactor helper function for setting / clearing GCR3 Vasant Hegde
2023-08-08 10:02 ` [PATCH 06/11] iommu/amd: Refactor helper function for attaching / detaching device Vasant Hegde
2023-08-08 15:39 ` Jason Gunthorpe
2023-08-11 10:07 ` Vasant Hegde
2023-08-11 13:20 ` Jason Gunthorpe
2023-08-11 16:50 ` Vasant Hegde
2023-08-11 23:50 ` Jason Gunthorpe
2023-08-15 4:19 ` Tian, Kevin
2023-08-15 5:33 ` Suthikulpanit, Suravee
2023-08-15 11:42 ` Jason Gunthorpe
2023-08-08 10:02 ` [PATCH 07/11] iommu/amd: Refactor protection_domain helper functions Vasant Hegde
2023-08-08 10:02 ` [PATCH 08/11] iommu/amd: Refactor GCR3 table " Vasant Hegde
2023-08-08 10:02 ` [PATCH 09/11] iommu/amd: Introduce helper functions for AMD IOMMU v2 driver Vasant Hegde
2023-08-08 15:49 ` Jason Gunthorpe
2023-08-11 1:34 ` Suthikulpanit, Suravee
2023-08-11 13:17 ` Jason Gunthorpe
2023-08-11 16:51 ` Suthikulpanit, Suravee
2023-08-08 10:02 ` [PATCH 10/11] iommu/amd/iommu_v2: Add support to switch default domain to SVA mode Vasant Hegde
2023-08-08 15:51 ` Jason Gunthorpe
2023-08-08 10:02 ` [PATCH 11/11] iommu/amd: Remove unused GCR3 table parameters from struct protection_domain Vasant Hegde
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=bcd2749c-d4de-fa8c-c865-ac9ed184ea17@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=vasant.hegde@amd.com \
--cc=wei.huang2@amd.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