From: Joerg Roedel <joro@8bytes.org>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
joao.m.martins@oracle.com, alejandro.j.jimenez@oracle.com,
boris.ostrovsky@oracle.com, jon.grimm@amd.com,
santosh.shukla@amd.com, vasant.hegde@amd.com,
kishon.vijayabraham@amd.com, jsnitsel@redhat.com
Subject: Re: [PATCH v3 0/5] iommu/amd: AVIC Interrupt Remapping Improvements
Date: Fri, 9 Jun 2023 14:47:37 +0200 [thread overview]
Message-ID: <ZIMfaVIoKlL-t8Sf@8bytes.org> (raw)
In-Reply-To: <20230530141137.14376-1-suravee.suthikulpanit@amd.com>
On Tue, May 30, 2023 at 10:11:32AM -0400, Suravee Suthikulpanit wrote:
> Suravee Suthikulpanit (4):
> iommu/amd: Remove the unused struct amd_ir_data.ref
> iommu/amd: Introduce Disable IRTE Caching Support
> iommu/amd: Do not Invalidate IRT when IRTE caching is disabled
> iommu/amd: Improving Interrupt Remapping Table Invalidation
>
> .../admin-guide/kernel-parameters.txt | 1 +
> drivers/iommu/amd/amd_iommu_types.h | 7 +-
> drivers/iommu/amd/init.c | 38 +++++++-
> drivers/iommu/amd/iommu.c | 97 ++++++++++---------
> 4 files changed, 94 insertions(+), 49 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2023-06-09 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 14:11 [PATCH v3 0/5] iommu/amd: AVIC Interrupt Remapping Improvements Suravee Suthikulpanit
2023-05-30 14:11 ` [PATCH v3 1/5] iommu/amd: Switch amd_iommu_update_ga() to use modify_irte_ga() Suravee Suthikulpanit
2023-05-30 14:11 ` [PATCH v3 2/5] iommu/amd: Remove the unused struct amd_ir_data.ref Suravee Suthikulpanit
2023-05-30 14:11 ` [PATCH v3 3/5] iommu/amd: Introduce Disable IRTE Caching Support Suravee Suthikulpanit
2023-05-30 14:11 ` [PATCH v3 4/5] iommu/amd: Do not Invalidate IRT when IRTE caching is disabled Suravee Suthikulpanit
2023-05-30 14:11 ` [PATCH v3 5/5] iommu/amd: Improving Interrupt Remapping Table Invalidation Suravee Suthikulpanit
2023-06-06 14:06 ` [PATCH v3 0/5] iommu/amd: AVIC Interrupt Remapping Improvements Suthikulpanit, Suravee
2023-06-09 12:47 ` 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=ZIMfaVIoKlL-t8Sf@8bytes.org \
--to=joro@8bytes.org \
--cc=alejandro.j.jimenez@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=joao.m.martins@oracle.com \
--cc=jon.grimm@amd.com \
--cc=jsnitsel@redhat.com \
--cc=kishon.vijayabraham@amd.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.