From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Cc: joro@8bytes.org, robin.murphy@arm.com, vasant.hegde@amd.com,
jgg@nvidia.com, kevin.tian@intel.com, jon.grimm@amd.com,
santosh.shukla@amd.com, pandoh@google.com, kumaranand@google.com
Subject: Re: [PATCH v4 0/6] iommu/amd: Use 128-bit cmpxchg operation to update DTE
Date: Mon, 23 Sep 2024 22:03:03 +0700 [thread overview]
Message-ID: <668fac7d-79e1-4cb6-bdf4-e15808cedc46@amd.com> (raw)
In-Reply-To: <20240916171805.324292-1-suravee.suthikulpanit@amd.com>
On 9/17/2024 12:17 AM, Suravee Suthikulpanit wrote:
> This series modifies current implementation to use 128-bit cmpxchg to
> update DTE when needed as specified in the AMD I/O Virtualization
> Techonology (IOMMU) Specification.
>
> Please note that I have verified with the hardware designer, and they have
> confirmed that the IOMMU hardware has always been implemented with 256-bit
> read. The next revision of the IOMMU spec will be updated to correctly
> describe this part. Therefore, I have updated the implementation to avoid
> unnecessary flushing.
>
> Changes in v4:
> * Patch 1: Update commit message
> * Patch 2:
> - Move get_dte256, clone_alias, dump_dte to patch 4
> - Introduce write_upper, write_lower
> - Introduce iommu_flush_sync_dte
> - Reimplement update_dte256
> * Patch 3: Remove spinlock since it is moved inside update_dte256()
> * Patch 4: Update clone_alias() and dump_dte()
> * Patch 5: Update clear_dte_entry()
>
> v3: https://lore.kernel.org/lkml/20240906121308.5013-1-suravee.suthikulpanit@amd.com/
> v2: https://lore.kernel.org/lkml/20240829180726.5022-1-suravee.suthikulpanit@amd.com/
> v1: https://lore.kernel.org/lkml/20240819161839.4657-1-suravee.suthikulpanit@amd.com/
>
> Thanks,
> Suravee
>
> Suravee Suthikulpanit (6):
> iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported
> iommu/amd: Introduce helper function to update 256-bit DTE
> iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers
> iommu/amd: Introduce helper function get_dte256()
> iommu/amd: Modify clear_dte_entry() to avoid in-place update
> iommu/amd: Lock DTE before updating the entry with WRITE_ONCE()
>
> drivers/iommu/amd/amd_iommu.h | 2 +
> drivers/iommu/amd/amd_iommu_types.h | 10 +-
> drivers/iommu/amd/init.c | 23 +-
> drivers/iommu/amd/iommu.c | 332 ++++++++++++++++++++--------
> 4 files changed, 265 insertions(+), 102 deletions(-)
>
I am rebasing and will resend this patch series.
Suravee
prev parent reply other threads:[~2024-09-23 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:17 [PATCH v4 0/6] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suravee Suthikulpanit
2024-09-16 17:18 ` [PATCH v4 1/6] iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported Suravee Suthikulpanit
2024-09-16 17:18 ` [PATCH v4 2/6] iommu/amd: Introduce helper function to update 256-bit DTE Suravee Suthikulpanit
2024-09-26 19:46 ` Jason Gunthorpe
2024-10-03 16:15 ` Suthikulpanit, Suravee
2024-10-03 18:54 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 3/6] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers Suravee Suthikulpanit
2024-09-26 19:56 ` Jason Gunthorpe
2024-10-03 16:16 ` Suthikulpanit, Suravee
2024-10-03 18:49 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 4/6] iommu/amd: Introduce helper function get_dte256() Suravee Suthikulpanit
2024-09-26 19:49 ` Jason Gunthorpe
2024-09-16 17:18 ` [PATCH v4 5/6] iommu/amd: Modify clear_dte_entry() to avoid in-place update Suravee Suthikulpanit
2024-09-26 19:54 ` Jason Gunthorpe
2024-10-03 16:15 ` Suthikulpanit, Suravee
2024-09-16 17:18 ` [PATCH v4 6/6] iommu/amd: Lock DTE before updating the entry with WRITE_ONCE() Suravee Suthikulpanit
2024-09-26 19:58 ` Jason Gunthorpe
2024-09-23 15:03 ` Suthikulpanit, Suravee [this message]
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=668fac7d-79e1-4cb6-bdf4-e15808cedc46@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--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=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