From: Joerg Roedel <joro@8bytes.org>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
robin.murphy@arm.com, vasant.hegde@amd.com, arnd@arndb.de,
ubizjak@gmail.com, linux-arch@vger.kernel.org, jgg@nvidia.com,
kevin.tian@intel.com, jon.grimm@amd.com, santosh.shukla@amd.com,
pandoh@google.com, kumaranand@google.com
Subject: Re: [PATCH v12 0/9] iommu/amd: Use 128-bit cmpxchg operation to update DTE
Date: Wed, 18 Dec 2024 09:38:09 +0100 [thread overview]
Message-ID: <Z2KJ8SGMoTfx_t76@8bytes.org> (raw)
In-Reply-To: <20241118054937.5203-1-suravee.suthikulpanit@amd.com>
On Mon, Nov 18, 2024 at 05:49:28AM +0000, Suravee Suthikulpanit wrote:
> Suravee Suthikulpanit (9):
> iommu/amd: Misc ACPI IVRS debug info clean up
> iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported
> iommu/amd: Introduce struct ivhd_dte_flags to store persistent DTE
> flags
> 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()
> iommu/amd: Remove amd_iommu_apply_erratum_63()
>
> drivers/iommu/amd/amd_iommu.h | 4 +-
> drivers/iommu/amd/amd_iommu_types.h | 41 ++-
> drivers/iommu/amd/init.c | 229 +++++++++--------
> drivers/iommu/amd/iommu.c | 378 +++++++++++++++++++++-------
> 4 files changed, 440 insertions(+), 212 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2024-12-18 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 5:49 [PATCH v12 0/9] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 1/9] iommu/amd: Misc ACPI IVRS debug info clean up Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 2/9] iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 3/9] iommu/amd: Introduce struct ivhd_dte_flags to store persistent DTE flags Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 4/9] iommu/amd: Introduce helper function to update 256-bit DTE Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 5/9] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 6/9] iommu/amd: Introduce helper function get_dte256() Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 7/9] iommu/amd: Modify clear_dte_entry() to avoid in-place update Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 8/9] iommu/amd: Lock DTE before updating the entry with WRITE_ONCE() Suravee Suthikulpanit
2024-11-18 5:49 ` [PATCH v12 9/9] iommu/amd: Remove amd_iommu_apply_erratum_63() Suravee Suthikulpanit
2024-12-18 8:38 ` Joerg Roedel [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=Z2KJ8SGMoTfx_t76@8bytes.org \
--to=joro@8bytes.org \
--cc=arnd@arndb.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=kevin.tian@intel.com \
--cc=kumaranand@google.com \
--cc=linux-arch@vger.kernel.org \
--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=ubizjak@gmail.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