From: Jason Gunthorpe <jgg@nvidia.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
joro@8bytes.org, robin.murphy@arm.com, vasant.hegde@amd.com,
kevin.tian@intel.com, jon.grimm@amd.com, santosh.shukla@amd.com,
pandoh@google.com, kumaranand@google.com
Subject: Re: [PATCH v7 06/10] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers
Date: Thu, 31 Oct 2024 09:53:06 -0300 [thread overview]
Message-ID: <20241031125306.GF10193@nvidia.com> (raw)
In-Reply-To: <20241031091624.4895-7-suravee.suthikulpanit@amd.com>
On Thu, Oct 31, 2024 at 09:16:20AM +0000, Suravee Suthikulpanit wrote:
> @@ -1148,6 +1146,28 @@ static bool copy_device_table(void)
> return true;
> }
>
> +struct dev_table_entry *amd_iommu_get_ivhd_dte_flags(u16 devid)
> +{
> + u16 f = 0, l = 0xFFFF;
> + struct ivhd_dte_flags *e;
> + struct dev_table_entry *dte = NULL;
> +
> + for_each_ivhd_dte_flags(e) {
Maybe the list head should be on the iommu? I don't know how long it
would be if it is worthwhile.
> + /*
> + * Need to go through the whole list to find the smallest range,
> + * which contains the devid. Then store it in f and l variables.
> + */
> + if ((e->devid_first >= devid) && (e->devid_last <= devid)) {
> + if (f < e->devid_first)
> + f = e->devid_first;
> + if (e->devid_last < l)
> + l = e->devid_last;
> + dte = &(e->dte);
> + }
f and l are never used, why calculate them?
Isn't (e->devid_first >= devid) not the right way to check if devid
falls within a range?
Based on the comment it seems like you want something like this??
struct dev_table_entry *amd_iommu_get_ivhd_dte_flags(u16 devid)
{
struct dev_table_entry *dte = NULL;
unsigned int best_len = UINT_MAX;
struct ivhd_dte_flags *e;
for_each_ivhd_dte_flags(e) {
/*
* Need to go through the whole list to find the smallest range,
* which contains the devid. Then store it in f and l variables.
*/
if ((e->devid_first <= devid) && (e->devid_last >= devid)) {
unsigned int len = e->devid_last - e->devid_first;
if (len < best_len) {
dte = &(e->dte);
best_len = len;
}
}
}
return dte;
}
(and it would be smart to sort the linked list by size, but again I
don't know how big it is if it is worthwile complexity)
The DTE code looks OK
Jason
next prev parent reply other threads:[~2024-10-31 12:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 9:16 [PATCH v7 00/10] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 01/10] iommu/amd: Misc ACPI IVRS debug info clean up Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 02/10] iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 03/10] asm/rwonce: Introduce [READ|WRITE]_ONCE() support for __int128 Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 04/10] iommu/amd: Introduce struct ivhd_dte_flags to store persistent DTE flags Suravee Suthikulpanit
2024-10-31 12:40 ` Jason Gunthorpe
2024-10-31 9:16 ` [PATCH v7 05/10] iommu/amd: Introduce helper function to update 256-bit DTE Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 06/10] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers Suravee Suthikulpanit
2024-10-31 12:53 ` Jason Gunthorpe [this message]
2024-10-31 16:18 ` Suthikulpanit, Suravee
2024-10-31 9:16 ` [PATCH v7 07/10] iommu/amd: Introduce helper function get_dte256() Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 08/10] iommu/amd: Modify clear_dte_entry() to avoid in-place update Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 09/10] iommu/amd: Lock DTE before updating the entry with WRITE_ONCE() Suravee Suthikulpanit
2024-10-31 9:16 ` [PATCH v7 10/10] iommu/amd: Remove amd_iommu_apply_erratum_63() Suravee Suthikulpanit
2024-10-31 12:56 ` 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=20241031125306.GF10193@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kumaranand@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pandoh@google.com \
--cc=robin.murphy@arm.com \
--cc=santosh.shukla@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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