From: Sairaj Kodilkar <sarunkod@amd.com>
To: <joro@8bytes.org>, <iommu@lists.linux.dev>
Cc: <suravee.suthikulpanit@amd.com>, <will@kernel.org>,
<robin.murphy@arm.com>, <vasant.hegde@amd.com>,
<sarunkod@amd.com>
Subject: [PATCH 0/4] iommu/amd: Enable support for up to 2K interrupts per
Date: Fri, 7 Mar 2025 15:28:18 +0530 [thread overview]
Message-ID: <20250307095822.2274-1-sarunkod@amd.com> (raw)
Newer versions of the AMD platform can support up to 2K interrupts per
function. This support can be enabled via field NumIntRemapMode in IOMMU
control register (MMIO offset 0x0018).
This series adds support to enable 2K interrupts per function on top of
v6.14-rc5.
Please see more details in [1]
[1] https://www.amd.com/content/dam/amd/en/documents/processor-tech-docs/specifications/48882_IOMMU.pdf
Kishon Vijay Abraham I (1):
iommu/amd: Enable support for up to 2K interrupts per function
Sairaj Kodilkar (3):
iommu/amd: Introduce generic function to set multibit feature value
iommu/amd: Replace slab cache allocator with page allocator
iommu/amd: Rename DTE_INTTABLEN* and MAX_IRQS_PER_TABLE macro
drivers/iommu/amd/amd_iommu_types.h | 27 ++++++-----
drivers/iommu/amd/init.c | 65 +++++++++++---------------
drivers/iommu/amd/iommu.c | 72 +++++++++++++++++++++--------
3 files changed, 94 insertions(+), 70 deletions(-)
--
2.34.1
next reply other threads:[~2025-03-07 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:58 Sairaj Kodilkar [this message]
2025-03-07 9:58 ` [PATCH 1/4] iommu/amd: Introduce generic function to set multibit feature value Sairaj Kodilkar
2025-03-07 9:58 ` [PATCH 2/4] iommu/amd: Replace slab cache allocator with page allocator Sairaj Kodilkar
2025-03-07 9:58 ` [PATCH 3/4] iommu/amd: Rename DTE_INTTABLEN* and MAX_IRQS_PER_TABLE macro Sairaj Kodilkar
2025-03-07 9:58 ` [PATCH 4/4] iommu/amd: Enable support for up to 2K interrupts per function Sairaj Kodilkar
2025-03-13 5:41 ` [PATCH 0/4] iommu/amd: Enable support for up to 2K interrupts per Vasant Hegde
2025-03-13 11:15 ` Joerg Roedel
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=20250307095822.2274-1-sarunkod@amd.com \
--to=sarunkod@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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