From: Joerg Roedel <joro@8bytes.org>
To: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
Cc: jsnitsel@redhat.com, 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
Subject: Re: [PATCH v2 4/5] iommu/amd: Do not Invalidate IRT when disable IRTE caching
Date: Tue, 23 May 2023 08:32:27 +0200 [thread overview]
Message-ID: <ZGxd-4mKvSgmYCvN@8bytes.org> (raw)
In-Reply-To: <700f08ad-0eb6-4ad6-329b-fe5b9cdb6a4f@amd.com>
Hi Suravee,
On Tue, May 23, 2023 at 10:38:59AM +0700, Suthikulpanit, Suravee wrote:
> Joerg, Please let me know if you would like me to send v3 with updated
> summary.
Yes, please send a v3 with all updates included.
Thanks,
Joerg
next prev parent reply other threads:[~2023-05-23 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 0:55 [PATCH v2 0/5] iommu/amd: AVIC Interrupt Remapping Improvements Suravee Suthikulpanit
2023-05-19 0:55 ` [PATCH v2 1/5] iommu/amd: Switch amd_iommu_update_ga() to use modify_irte_ga() Suravee Suthikulpanit
2023-05-23 0:02 ` Jerry Snitselaar
2023-05-19 0:55 ` [PATCH v2 2/5] iommu/amd: Remove the unused struct amd_ir_data.ref Suravee Suthikulpanit
2023-05-23 0:03 ` Jerry Snitselaar
2023-05-19 0:55 ` [PATCH v2 3/5] iommu/amd: Introduce Disable IRTE Caching Support Suravee Suthikulpanit
2023-05-22 17:02 ` Alejandro Jimenez
2023-05-23 0:10 ` Jerry Snitselaar
2023-05-19 0:55 ` [PATCH v2 4/5] iommu/amd: Do not Invalidate IRT when disable IRTE caching Suravee Suthikulpanit
2023-05-23 0:17 ` jsnitsel
2023-05-23 3:38 ` Suthikulpanit, Suravee
2023-05-23 6:32 ` Joerg Roedel [this message]
2023-05-19 0:55 ` [PATCH v2 5/5] iommu/amd: Improving Interrupt Remapping Table Invalidation Suravee Suthikulpanit
2023-05-23 0:22 ` Jerry Snitselaar
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=ZGxd-4mKvSgmYCvN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox