From: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
To: Vasant Hegde <vasant.hegde@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 v3 7/8] iommu/amd: Add debugfs support to dump IRT Table
Date: Mon, 17 Mar 2025 16:56:39 +0530 [thread overview]
Message-ID: <205328f3-8b1b-4e1d-afa8-da6a123866e2@amd.com> (raw)
In-Reply-To: <d5dc3ba1-187c-4ce4-b7a9-eea95a7f043f@amd.com>
Hi Vasant,
On 3/13/2025 4:33 PM, Vasant Hegde wrote:
> Hi,
>
>
> On 2/6/2025 11:30 AM, 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 | 89 +++++++++++++++++++++++++++++++++++++
>> 1 file changed, 89 insertions(+)
>>
>> diff --git a/drivers/iommu/amd/debugfs.c b/drivers/iommu/amd/debugfs.c
>> index 1377795814d1..0aff1d616108 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;
>>
>> @@ -250,6 +251,92 @@ 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)
>> +{
>> + struct irte_ga *ptr, *irte;
>> + int index;
>> +
>> + for (index = 0; index < MAX_IRQS_PER_TABLE; 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);
>
> Can you please space between words so that its easy to read?
Sure. Will update in v4.
Thanks
Dheeraj
>
> -Vasant
>
>
next prev parent reply other threads:[~2025-03-17 11:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 5:59 [PATCH v3 0/8] Introduce debugfs support in IOMMU Dheeraj Kumar Srivastava
2025-02-06 5:59 ` [PATCH v3 1/8] iommu/amd: Refactor AMD IOMMU debugfs initial setup Dheeraj Kumar Srivastava
2025-03-13 10:27 ` Vasant Hegde
2025-02-06 5:59 ` [PATCH v3 2/8] iommu/amd: Add debugfs support to dump IOMMU MMIO registers Dheeraj Kumar Srivastava
2025-03-13 10:28 ` Vasant Hegde
2025-03-17 11:22 ` Dheeraj Kumar Srivastava
2025-02-06 5:59 ` [PATCH v3 3/8] iommu/amd: Add debugfs support to dump IOMMU Capability registers Dheeraj Kumar Srivastava
2025-03-13 10:32 ` Vasant Hegde
2025-03-17 11:23 ` Dheeraj Kumar Srivastava
2025-02-06 5:59 ` [PATCH v3 4/8] iommu/amd: Add debugfs support to dump IOMMU command buffer Dheeraj Kumar Srivastava
2025-03-13 10:38 ` Vasant Hegde
2025-03-17 11:24 ` Dheeraj Kumar Srivastava
2025-02-06 6:00 ` [PATCH v3 5/8] iommu/amd: Add support for device id user input Dheeraj Kumar Srivastava
2025-03-13 10:52 ` Vasant Hegde
2025-03-17 11:25 ` Dheeraj Kumar Srivastava
2025-02-06 6:00 ` [PATCH v3 6/8] iommu/amd: Add debugfs support to dump device table Dheeraj Kumar Srivastava
2025-02-06 6:00 ` [PATCH v3 7/8] iommu/amd: Add debugfs support to dump IRT Table Dheeraj Kumar Srivastava
2025-03-13 11:03 ` Vasant Hegde
2025-03-17 11:26 ` Dheeraj Kumar Srivastava [this message]
2025-02-06 6:00 ` [PATCH v3 8/8] iommu/amd: Add documentation for AMD IOMMU debugfs support Dheeraj Kumar Srivastava
2025-02-06 8:56 ` [PATCH v3 0/8] Introduce debugfs support in IOMMU Suthikulpanit, Suravee
2025-03-07 8:17 ` 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=205328f3-8b1b-4e1d-afa8-da6a123866e2@amd.com \
--to=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=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