From: Vasant Hegde <vasant.hegde@amd.com>
To: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>,
joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
robin.murphy@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux.dev
Subject: Re: [PATCH v6 6/8] iommu/amd: Add debugfs support to dump device table
Date: Sun, 29 Jun 2025 11:08:43 +0530 [thread overview]
Message-ID: <5b360e8a-03bf-4886-8134-8e4ab5a9f485@amd.com> (raw)
In-Reply-To: <20250604163647.1439-7-dheerajkumar.srivastava@amd.com>
Dheeraj,
On 6/4/2025 10:06 PM, Dheeraj Kumar Srivastava wrote:
> IOMMU uses device table data structure to get per-device information for
> DMA remapping, interrupt remapping, and other functionalities. It's a
> valuable data structure to visualize for debugging issues related to
> IOMMU.
>
> eg.
> -> To dump device table entry for a particular device
> #echo 0000:c4:00.0 > /sys/kernel/debug/iommu/amd/devid
> #cat /sys/kernel/debug/iommu/amd/devtbl
>
> or
>
> #echo c4:00.0 > /sys/kernel/debug/iommu/amd/devid
> #cat /sys/kernel/debug/iommu/amd/devtbl
>
> Signed-off-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
> ---
> drivers/iommu/amd/debugfs.c | 49 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
>
> diff --git a/drivers/iommu/amd/debugfs.c b/drivers/iommu/amd/debugfs.c
> index 8b57ab4ab809..38d3cab5fd8d 100644
> --- a/drivers/iommu/amd/debugfs.c
> +++ b/drivers/iommu/amd/debugfs.c
> @@ -207,6 +207,53 @@ static int devid_show(struct seq_file *m, void *unused)
> }
> DEFINE_SHOW_STORE_ATTRIBUTE(devid);
>
> +static void dump_dte(struct seq_file *m, struct amd_iommu_pci_seg *pci_seg, u16 devid)
> +{
> + struct dev_table_entry *dev_table;
> + struct amd_iommu *iommu;
> +
> + iommu = pci_seg->rlookup_table[devid];
> + if (!iommu)
> + return;
> +
> + dev_table = get_dev_table(iommu);
> + if (!dev_table) {
> + seq_puts(m, "Device table not found");
> + return;
> + }
> +
> + seq_printf(m, "%-12s %16s %16s %16s %16s iommu\n", "DeviceId",
> + "QWORD[3]", "QWORD[2]", "QWORD[1]", "QWORD[0]");
> + seq_printf(m, "%04x:%02x:%02x.%x ", pci_seg->id, PCI_BUS_NUM(devid),
> + PCI_SLOT(devid), PCI_FUNC(devid));
> + for (int i = 3; i >= 0; --i)
> + seq_printf(m, "%016llx ", dev_table[devid].data[i]);
> + seq_printf(m, "iommu%d\n", iommu->index);
> +}
> +
> +static int iommu_devtbl_show(struct seq_file *m, void *unused)
> +{
> + struct amd_iommu_pci_seg *pci_seg;
> + u16 seg, devid;
> +
> + if (sbdf < 0) {
> + seq_puts(m, "Please provide valid device id input\n");
Where? This should clearly indicate where to provide device id.
-Vasant
next prev parent reply other threads:[~2025-06-29 5:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 16:36 [PATCH v6 0/8] Introduce debugfs support in IOMMU 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 [this message]
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 ` [PATCH v6 0/8] Introduce debugfs support in IOMMU Dheeraj Kumar Srivastava
2025-06-27 6:53 ` 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=5b360e8a-03bf-4886-8134-8e4ab5a9f485@amd.com \
--to=vasant.hegde@amd.com \
--cc=dheerajkumar.srivastava@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®