From: Vasant Hegde <vasant.hegde@amd.com>
To: <iommu@lists.linux.dev>, <joro@8bytes.org>
Cc: <suravee.suthikulpanit@amd.com>, Vasant Hegde <vasant.hegde@amd.com>
Subject: [PATCH v2 0/2] iommu/amd: Interrupt handling improvements
Date: Mon, 19 Jun 2023 13:30:06 +0000 [thread overview]
Message-ID: <20230619133008.6221-1-vasant.hegde@amd.com> (raw)
AMD IOMMU has three different logs/interrupts (Event, PPR and GA).
Currently, the IOMMU driver consolidates interrupts for all three logs to
a single interrupt. This could become a bottleneck when enable GA and PPR
logs simultaneously. Hence separate these interrupt to prevent potential
performance issue.
This series applies on top of PPR overflow support patchset [1].
[1] https://lore.kernel.org/linux-iommu/20230619132346.6021-1-vasant.hegde@amd.com/
Changes from v1 -> v2:
- Moved GA log interrupt under CONFIG_IRQ_REMAP
- Updated patch description
V1 : https://lore.kernel.org/linux-iommu/20230609102025.6498-1-vasant.hegde@amd.com/
Vasant Hegde (2):
iommu/amd: Refactor IOMMU interrupt handling logic for Event, PPR, and GA logs
iommu/amd: Enable separate interrupt for PPR and GA log
drivers/iommu/amd/amd_iommu.h | 3 +
drivers/iommu/amd/amd_iommu_types.h | 9 +++
drivers/iommu/amd/init.c | 50 +++++++++++----
drivers/iommu/amd/iommu.c | 95 ++++++++++++++++-------------
4 files changed, 101 insertions(+), 56 deletions(-)
--
2.31.1
next reply other threads:[~2023-06-19 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 13:30 Vasant Hegde [this message]
2023-06-19 13:30 ` [PATCH v2 1/2] iommu/amd: Refactor IOMMU interrupt handling logic for Event, PPR, and GA logs Vasant Hegde
2023-06-19 13:30 ` [PATCH v2 2/2] iommu/amd: Enable separate interrupt for PPR and GA log Vasant Hegde
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=20230619133008.6221-1-vasant.hegde@amd.com \
--to=vasant.hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=suravee.suthikulpanit@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;
as well as URLs for NNTP newsgroup(s).