From: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
To: joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
robin.murphy@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev, Vasant.Hegde@amd.com
Subject: Re: [PATCH v6 0/8] Introduce debugfs support in IOMMU
Date: Thu, 26 Jun 2025 11:27:54 +0530 [thread overview]
Message-ID: <dbec455c-74a0-4f91-8b8c-7b995c6e3e9c@amd.com> (raw)
In-Reply-To: <20250604163647.1439-1-dheerajkumar.srivastava@amd.com>
Hi,
Just a friendly reminder to review the patch series. Your valuable
feedback would be greatly appreciated to help us move forward.
Thanks
Dheeraj
On 6/4/2025 10:06 PM, Dheeraj Kumar Srivastava wrote:
> Introducing debugfs support in AMD/IOMMU driver that will allow
> userspace to dump below IOMMU information
> 1) MMIO and Capability register per IOMMU
> 2) Command buffer
> 3) Device table entry
> 4) Interrupt remapping table entry
>
> Analyzing contents of IOMMU data structures helps in understanding IOMMU
> capabilities and behavior and debug issues faster.
>
> 1. MMIO and Capability registers - Add support to dump MMIO and Capability
> registers per IOMMU.
>
> Example:
> a. Write MMIO register offset to dump it
> $ echo 0x18 > /sys/kernel/debug/iommu/amd/iommu00/mmio
> $ cat /sys/kernel/debug/iommu/amd/iommu00/mmio
>
> Output:
> $ Offset:0x18 Value:0x000c22000003f48d
>
> b. Write capability register offset to dump it
> $ echo 0x10 > /sys/kernel/debug/iommu/amd/iommu00/capability
> $ cat /sys/kernel/debug/iommu/amd/iommu00/capability
>
> Output:
> $ Offset:0x10 Value:0x00203040
>
> 2. Command buffer - Add support to dump per IOMMU command buffer.
>
> Example:
> a. cat /sys/kernel/debug/iommu/amd/iommu00/cmdbuf
>
> Output:
> CMD Buffer Head Offset:339 Tail Offset:339
> 0: 00835001 10000001 00009900 00000000
> 1: 00000000 30000005 fffff003 7fffffff
> 2: 00835001 10000001 00009901 00000000
> 3: 00000000 30000005 fffff003 7fffffff
> 4: 00835001 10000001 00009902 00000000
> ........................................
> ........................................
> ........................................
>
> 3. Device table - Add support to dump device table per IOMMU.
>
> Example:
> a. Write device id to dump device table entry for that device
> $ echo 0000:01:00.0 > /sys/kernel/debug/iommu/amd/devid
> $ cat /sys/kernel/debug/iommu/amd/devid
>
> Output:
> 0000:01:00.0
>
> Dump the device table entry for the input given
> $ cat /sys/kernel/debug/iommu/amd/devtbl
>
> Output:
> DeviceId QWORD[3] QWORD[2] QWORD[1] QWORD[0] iommu
> 0000:01:00.0 0000000000000000 20000001373b8013 0000000000000038 6000000114d7b603 iommu3
>
> b. Write device id to dump device table entry for that device
> $ echo 01:00.0 > /sys/kernel/debug/iommu/amd/devid
> $ cat /sys/kernel/debug/iommu/amd/devid
>
> Output:
> 0000:01:00.0
>
> Dump the device table entry for the input given
> $ cat /sys/kernel/debug/iommu/amd/devtbl
>
> Output:
> DeviceId QWORD[3] QWORD[2] QWORD[1] QWORD[0] iommu
> 0000:01:00.0 0000000000000000 20000001373b8013 0000000000000038 6000000114d7b603 iommu3
>
> 4. Interrupt remapping table - Add support to dump IRT table valid entries in
> "iommu_irqtbl" file. This supports user input to dump IRT entry for a
> specific pci device.
>
> Example:
> a. Write device id to dump device table entry for that device
> $ echo 0000:01:00.0 > /sys/kernel/debug/iommu/amd/devid
> $ cat /sys/kernel/debug/iommu/amd/devid
>
> Output:
> 0000:01:00.0
>
> Dump the device table entry for the input given
> $ cat /sys/kernel/debug/iommu/amd/irtbl
>
> Output:
> DeviceId 0000:01:00.0
> IRT[0000] 0000000000000020 0000000000000241
> IRT[0001] 0000000000000020 0000000000000841
> IRT[0002] 0000000000000020 0000000000002041
> IRT[0003] 0000000000000020 0000000000008041
> IRT[0004] 0000000000000020 0000000000020041
> ..........................................
> ..........................................
> ..........................................
>
> b. Write device id to dump device table entry for that device
> $ echo 01:00.0 > /sys/kernel/debug/iommu/amd/devid
> $ cat /sys/kernel/debug/iommu/amd/devid
>
> Output:
> 0000:01:00.0
>
> Dump the device table entry for the input given
> $ cat /sys/kernel/debug/iommu/amd/irttbl
>
> Output:
> Device 0000:01:00.0
> IRT[0000] 0000000000000020 0000000000000241
> IRT[0001] 0000000000000020 0000000000000841
> IRT[0002] 0000000000000020 0000000000002041
> IRT[0003] 0000000000000020 0000000000008041
> IRT[0004] 0000000000000020 0000000000020041
> ..........................................
> ..........................................
> ..........................................
>
> Changes since v5:
> -> Patch 7/8: Use macros to fetch IRT table length for DTE.
>
> Changes since v4:
> -> Maintain per IOMMU variable for mmio_offset and capability_offset.
> -> Get intrrupt table length from DTE instead of using MAX_IRQS_PER_TABLE.
>
> Changes since v3:
> -> Patch 2/8: Print 64 bits instead of 32 bits for MMIO registers dump. Since most of
> the MMIO registers are 64 bits.
> -> Patch 5/8: Update commit message with the need to add support for device_id input.
> -> Patch 3/8: Throw error message mentioning valid capability offset range if user capability
> offset's input is not in valid range and input fails.
>
> Changes since v2:
> -> Patch 2/8 and 3/8: Use single file mmio and capability for input and output registers
> offset and register's dump respctively.
> -> Patch 8/8: Correct path for files "irqtbl" and "devtbl" in Documentation
>
> Changes since v1:
> -> Patch 2/8 and 3/8: Use kstrtou32_from_user() instead of memdup_user_nul() --> kstrtou32()
> -> Patch 4/8: Dump command buffer head and tail offset instead of head and tail pointer registers.
> -> Patch 8/8: Fix bot reported warning on v1 patch series.
>
> Dheeraj Kumar Srivastava (8):
> iommu/amd: Refactor AMD IOMMU debugfs initial setup
> iommu/amd: Add debugfs support to dump IOMMU MMIO registers
> iommu/amd: Add debugfs support to dump IOMMU Capability registers
> iommu/amd: Add debugfs support to dump IOMMU command buffer
> iommu/amd: Add support for device id user input
> iommu/amd: Add debugfs support to dump device table
> iommu/amd: Add debugfs support to dump IRT Table
> iommu/amd: Add documentation for AMD IOMMU debugfs support
>
> Documentation/ABI/testing/debugfs-amd-iommu | 114 ++++++
> drivers/iommu/amd/amd_iommu.h | 4 +-
> drivers/iommu/amd/amd_iommu_types.h | 9 +
> drivers/iommu/amd/debugfs.c | 377 +++++++++++++++++++-
> drivers/iommu/amd/init.c | 5 +-
> drivers/iommu/amd/iommu.c | 7 -
> 6 files changed, 495 insertions(+), 21 deletions(-)
> create mode 100644 Documentation/ABI/testing/debugfs-amd-iommu
>
next prev parent reply other threads:[~2025-06-26 5:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 16:36 Dheeraj Kumar Srivastava
2025-06-04 16:36 ` [PATCH v6 1/8] iommu/amd: Refactor AMD IOMMU debugfs initial setup Dheeraj Kumar Srivastava
2025-06-04 16:36 ` [PATCH v6 2/8] iommu/amd: Add debugfs support to dump IOMMU MMIO registers Dheeraj Kumar Srivastava
2025-06-29 5:46 ` Vasant Hegde
2025-06-04 16:36 ` [PATCH v6 3/8] iommu/amd: Add debugfs support to dump IOMMU Capability registers Dheeraj Kumar Srivastava
2025-06-04 16:36 ` [PATCH v6 4/8] iommu/amd: Add debugfs support to dump IOMMU command buffer Dheeraj Kumar Srivastava
2025-06-04 16:36 ` [PATCH v6 5/8] iommu/amd: Add support for device id user input Dheeraj Kumar Srivastava
2025-06-04 16:36 ` [PATCH v6 6/8] iommu/amd: Add debugfs support to dump device table Dheeraj Kumar Srivastava
2025-06-29 5:38 ` Vasant Hegde
2025-06-04 16:36 ` [PATCH v6 7/8] iommu/amd: Add debugfs support to dump IRT Table Dheeraj Kumar Srivastava
2025-06-29 5:42 ` Vasant Hegde
2025-06-04 16:36 ` [PATCH v6 8/8] iommu/amd: Add documentation for AMD IOMMU debugfs support Dheeraj Kumar Srivastava
2025-06-26 5:57 ` Dheeraj Kumar Srivastava [this message]
2025-06-27 6:53 ` [PATCH v6 0/8] Introduce debugfs support in IOMMU Joerg Roedel
2025-06-29 5:54 ` Vasant Hegde
2025-07-02 9:45 ` Dheeraj Kumar Srivastava
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=dbec455c-74a0-4f91-8b8c-7b995c6e3e9c@amd.com \
--to=dheerajkumar.srivastava@amd.com \
--cc=Vasant.Hegde@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@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
all inboxes | Powered by JetHome®