From: Vasant Hegde <vasant.hegde@amd.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: iommu@lists.linux.dev, joro@8bytes.org,
suravee.suthikulpanit@amd.com, wei.huang2@amd.com,
jsnitsel@redhat.com
Subject: Re: [PATCH v4 08/14] iommu/amd: Consolidate feature detection and reporting logic
Date: Wed, 16 Aug 2023 12:12:40 +0530 [thread overview]
Message-ID: <aa1d48a7-9991-f32f-191a-2e71c623e532@amd.com> (raw)
In-Reply-To: <ZNvEjom6RD9v8Abc@ziepe.ca>
Jason,
On 8/16/2023 12:01 AM, Jason Gunthorpe wrote:
> On Tue, Aug 15, 2023 at 10:21:56AM +0000, Vasant Hegde wrote:
>
>> diff --git a/drivers/iommu/amd/amd_iommu.h b/drivers/iommu/amd/amd_iommu.h
>> index 6bf55de9fbeb..242e25ba2f93 100644
>> --- a/drivers/iommu/amd/amd_iommu.h
>> +++ b/drivers/iommu/amd/amd_iommu.h
>> @@ -90,9 +90,19 @@ static inline bool is_rd890_iommu(struct pci_dev *pdev)
>> (pdev->device == PCI_DEVICE_ID_RD890_IOMMU);
>> }
>>
>> -static inline bool iommu_feature(struct amd_iommu *iommu, u64 mask)
>> +static inline bool check_feature(u64 mask)
>> {
>> - return !!(iommu->features & mask);
>> + return !!(amd_iommu_efr & mask);
>> +}
>> +
>> +static inline bool check_feature2(u64 mask)
>> +{
>> + return !!(amd_iommu_efr2 & mask);
>> +}
>
> You don't need the !! when returning a bool
Sure. Will fix it.
>
>> @@ -2012,8 +2002,8 @@ static ssize_t amd_iommu_show_features(struct device *dev,
>> struct device_attribute *attr,
>> char *buf)
>> {
>> - struct amd_iommu *iommu = dev_to_amd_iommu(dev);
>> - return sysfs_emit(buf, "%llx:%llx\n", iommu->features2, iommu->features);
>> + return sysfs_emit(buf, "EFR:%llx, EFR2:%llx\n",
>> + amd_iommu_efr, amd_iommu_efr2);
>> }
>> static DEVICE_ATTR(features, S_IRUGO, amd_iommu_show_features, NULL);
>
> Can't do this, sysfs is ABI (and it should have not have returned two
> values in the first place, Greg would reject it)
Correct. Its existing ABI. Will fix it.
-Vasant
next prev parent reply other threads:[~2023-08-16 6:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 10:21 [PATCH v4 00/14] iommu/amd: SVA Support (Part 1) - cleanup/refactoring Vasant Hegde
2023-08-15 10:21 ` [PATCH v4 01/14] iommu/amd: Remove unused amd_io_pgtable.pt_root variable Vasant Hegde
2023-08-16 15:37 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 02/14] iommu/amd: Consolidate timeout pre-define to amd_iommu_type.h Vasant Hegde
2023-08-16 15:39 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 03/14] iommu/amd: Consolidate logic to allocate protection domain Vasant Hegde
2023-08-16 15:42 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 04/14] iommu/amd: Refactor protection domain allocation code Vasant Hegde
2023-08-16 16:18 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 05/14] iommu/amd: Introduce helper functions for managing GCR3 table Vasant Hegde
2023-08-15 14:47 ` Jason Gunthorpe
2023-08-16 23:18 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 06/14] iommu/amd: Do not set amd_iommu_pgtable in pass-through mode Vasant Hegde
2023-08-16 16:26 ` Jerry Snitselaar
2023-08-15 10:21 ` [PATCH v4 07/14] iommu/amd: Miscellaneous clean up when free domain Vasant Hegde
2023-08-15 10:21 ` [PATCH v4 08/14] iommu/amd: Consolidate feature detection and reporting logic Vasant Hegde
2023-08-15 18:31 ` Jason Gunthorpe
2023-08-16 6:42 ` Vasant Hegde [this message]
2023-08-15 10:21 ` [PATCH v4 09/14] iommu/amd: Modify logic for checking GT and PPR features Vasant Hegde
2023-08-15 18:32 ` Jason Gunthorpe
2023-08-15 10:21 ` [PATCH v4 10/14] iommu/amd: Rename ats related variables Vasant Hegde
2023-08-15 10:21 ` [PATCH v4 11/14] iommu/amd: Introduce iommu_dev_data.ppr Vasant Hegde
2023-08-15 18:33 ` Jason Gunthorpe
2023-08-16 7:19 ` Vasant Hegde
2023-08-15 10:22 ` [PATCH v4 12/14] iommu/amd: Introduce iommu_dev_data.flags to track device capabilities Vasant Hegde
2023-08-15 18:34 ` Jason Gunthorpe
2023-08-16 7:22 ` Vasant Hegde
2023-08-15 10:22 ` [PATCH v4 13/14] iommu/amd: Enable device ATS/PASID/PRI capabilities independently Vasant Hegde
2023-08-15 10:22 ` [PATCH v4 14/14] iommu/amd: Initialize iommu_device->max_pasids Vasant Hegde
2023-08-15 18:35 ` 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=aa1d48a7-9991-f32f-191a-2e71c623e532@amd.com \
--to=vasant.hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=suravee.suthikulpanit@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