mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 7/8] iommu/amd: Add debugfs support to dump IRT Table
Date: Sun, 29 Jun 2025 11:12:38 +0530	[thread overview]
Message-ID: <6f70ae62-0f5c-4620-a9a1-4720ac995b08@amd.com> (raw)
In-Reply-To: <20250604163647.1439-8-dheerajkumar.srivastava@amd.com>

Dheeraj,


On 6/4/2025 10:06 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 | 108 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 108 insertions(+)
> 
> diff --git a/drivers/iommu/amd/debugfs.c b/drivers/iommu/amd/debugfs.c
> index 38d3cab5fd8d..7a056ebcc7c3 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,111 @@ 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 = dev_table[devid].data[2] & DTE_INTTABLEN_MASK;
> +	if (int_tab_len != DTE_INTTABLEN_512 && int_tab_len != DTE_INTTABLEN_2K) {
> +		seq_puts(m, "The device's DTE contains an invalid IRT length value.");
> +		return;
> +	}
> +
> +	seq_printf(m, "DeviceId %04x:%02x:%02x.%x\n", pci_seg->id, PCI_BUS_NUM(devid),
> +		   PCI_SLOT(devid), PCI_FUNC(devid));
> +
> +	raw_spin_lock_irqsave(&table->lock, flags);
> +	if (AMD_IOMMU_GUEST_IR_GA(amd_iommu_guest_ir))
> +		dump_128_irte(m, table, BIT(int_tab_len >> 1));
> +	else
> +		dump_32_irte(m, table, BIT(int_tab_len >> 1));
> +	seq_puts(m, "\n");
> +	raw_spin_unlock_irqrestore(&table->lock, flags);
> +}
> +
> +static int iommu_irqtbl_show(struct seq_file *m, void *unused)
> +{
> +	struct amd_iommu_pci_seg *pci_seg;
> +	u16 devid, seg;
> +
> +	if (!irq_remapping_enabled) {
> +		seq_puts(m, "Interrupt remapping is disabled\n");
> +		return 0;
> +	}
> +
> +	if (sbdf < 0) {
> +		seq_puts(m, "Please provide valid device id input\n");

Again same as previous patch comment. Please add proper description so that user
know where to input devid.

-Vasant


  reply	other threads:[~2025-06-29  5:42 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
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 [this message]
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=6f70ae62-0f5c-4620-a9a1-4720ac995b08@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®