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 v5 7/8] iommu/amd: Add debugfs support to dump IRT Table
Date: Thu, 1 May 2025 15:36:03 +0530 [thread overview]
Message-ID: <a7d4929b-f7ff-4ce5-800e-79df3816d9d6@amd.com> (raw)
In-Reply-To: <20250407173500.1827-8-dheerajkumar.srivastava@amd.com>
On 4/7/2025 11:04 PM, Dheeraj Kumar Srivastava wrote:
> In cases where we have an issue in the device interrupt path with IOMMU
> interrupt remapping enabled, dumping valid IRT table entries for the device
> is very useful and good input for debugging the issue.
>
> eg.
> -> To dump irte entries for a particular device
> #echo "c4:00.0" > /sys/kernel/debug/iommu/amd/devid
> #cat /sys/kernel/debug/iommu/amd/irqtbl | less
>
> or
>
> #echo "0000:c4:00.0" > /sys/kernel/debug/iommu/amd/devid
> #cat /sys/kernel/debug/iommu/amd/irqtbl | less
>
> Signed-off-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
> ---
> drivers/iommu/amd/debugfs.c | 106 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 106 insertions(+)
>
> diff --git a/drivers/iommu/amd/debugfs.c b/drivers/iommu/amd/debugfs.c
> index c6ff47561afb..28fe546e0bc0 100644
> --- a/drivers/iommu/amd/debugfs.c
> +++ b/drivers/iommu/amd/debugfs.c
> @@ -11,6 +11,7 @@
> #include <linux/pci.h>
>
> #include "amd_iommu.h"
> +#include "../irq_remapping.h"
>
> static struct dentry *amd_iommu_debugfs;
>
> @@ -254,6 +255,109 @@ static int iommu_devtbl_show(struct seq_file *m, void *unused)
> }
> DEFINE_SHOW_ATTRIBUTE(iommu_devtbl);
>
> +static void dump_128_irte(struct seq_file *m, struct irq_remap_table *table, u16 int_tab_len)
> +{
> + struct irte_ga *ptr, *irte;
> + int index;
> +
> + for (index = 0; index < int_tab_len; index++) {
> + ptr = (struct irte_ga *)table->table;
> + irte = &ptr[index];
> +
> + if (AMD_IOMMU_GUEST_IR_VAPIC(amd_iommu_guest_ir) &&
> + !irte->lo.fields_vapic.valid)
> + continue;
> + else if (!irte->lo.fields_remap.valid)
> + continue;
> + seq_printf(m, "IRT[%04d] %016llx %016llx\n", index, irte->hi.val, irte->lo.val);
> + }
> +}
> +
> +static void dump_32_irte(struct seq_file *m, struct irq_remap_table *table, u16 int_tab_len)
> +{
> + union irte *ptr, *irte;
> + int index;
> +
> + for (index = 0; index < int_tab_len; index++) {
> + ptr = (union irte *)table->table;
> + irte = &ptr[index];
> +
> + if (!irte->fields.valid)
> + continue;
> + seq_printf(m, "IRT[%04d] %08x\n", index, irte->val);
> + }
> +}
> +
> +static void dump_irte(struct seq_file *m, u16 devid, struct amd_iommu_pci_seg *pci_seg)
> +{
> + struct dev_table_entry *dev_table;
> + struct irq_remap_table *table;
> + struct amd_iommu *iommu;
> + unsigned long flags;
> + u16 int_tab_len;
> +
> + table = pci_seg->irq_lookup_table[devid];
> + if (!table) {
> + seq_printf(m, "IRQ lookup table not set for %04x:%02x:%02x:%x\n",
> + pci_seg->id, PCI_BUS_NUM(devid), PCI_SLOT(devid), PCI_FUNC(devid));
> + return;
> + }
> +
> + 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;
> + }
> +
> + int_tab_len = 1 << ((dev_table[devid].data[2] >> 1) & 0xfULL);
This is hard to read. Please use the macros like FIELD_GET
> + if (int_tab_len > 2048)
s/2048/MAX_IRQS_PER_TABLE_2K/
-Vasant
next prev parent reply other threads:[~2025-05-01 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 17:34 [PATCH v5 0/8] Introduce debugfs support in IOMMU Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 1/8] iommu/amd: Refactor AMD IOMMU debugfs initial setup Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 2/8] iommu/amd: Add debugfs support to dump IOMMU MMIO registers Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 3/8] iommu/amd: Add debugfs support to dump IOMMU Capability registers Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 4/8] iommu/amd: Add debugfs support to dump IOMMU command buffer Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 5/8] iommu/amd: Add support for device id user input Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 6/8] iommu/amd: Add debugfs support to dump device table Dheeraj Kumar Srivastava
2025-04-07 17:34 ` [PATCH v5 7/8] iommu/amd: Add debugfs support to dump IRT Table Dheeraj Kumar Srivastava
2025-05-01 10:06 ` Vasant Hegde [this message]
2025-06-04 16:16 ` Dheeraj Kumar Srivastava
2025-04-07 17:35 ` [PATCH v5 8/8] iommu/amd: Add documentation for AMD IOMMU debugfs support 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=a7d4929b-f7ff-4ce5-800e-79df3816d9d6@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®