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 3/8] iommu/amd: Add debugfs support to dump IOMMU Capability registers
Date: Mon, 17 Mar 2025 16:53:33 +0530 [thread overview]
Message-ID: <3c14597f-e5dd-4e43-bd4a-6f7a6d08afa7@amd.com> (raw)
In-Reply-To: <fbb7d901-25b6-49c7-abeb-4e76451c197f@amd.com>
Hi Vasant,
On 3/13/2025 4:02 PM, Vasant Hegde wrote:
> Dheeraj,
>
>
> On 2/6/2025 11:29 AM, Dheeraj Kumar Srivastava wrote:
>> IOMMU Capability registers defines capabilities of IOMMU and information
>> needed for initialising MMIO registers and device table. This is useful
>> to dump these registers for debugging IOMMU related issues.
>>
>> e.g.To get capability registers value for iommu<x>
>> # echo "0x10" > /sys/kernel/debug/iommu/amd/iommu00/capability
>> # cat /sys/kernel/debug/iommu/amd/iommu00/capability
>>
>> Signed-off-by: Dheeraj Kumar Srivastava <dheerajkumar.srivastava@amd.com>
>> ---
>> drivers/iommu/amd/debugfs.c | 47 +++++++++++++++++++++++++++++++++++++
>> 1 file changed, 47 insertions(+)
>>
>> diff --git a/drivers/iommu/amd/debugfs.c b/drivers/iommu/amd/debugfs.c
>> index b16b62ae7111..dc5fdc905754 100644
>> --- a/drivers/iommu/amd/debugfs.c
>> +++ b/drivers/iommu/amd/debugfs.c
>> @@ -18,6 +18,7 @@ static struct dentry *amd_iommu_debugfs;
>> #define OFS_IN_SZ 8
>>
>> static int mmio_offset = -1;
>> +static int cap_offset = -1;
>>
>> static ssize_t iommu_mmio_write(struct file *filp, const char __user *ubuf,
>> size_t cnt, loff_t *ppos)
>> @@ -58,6 +59,50 @@ static int iommu_mmio_show(struct seq_file *m, void *unused)
>> }
>> DEFINE_SHOW_STORE_ATTRIBUTE(iommu_mmio);
>>
>> +static ssize_t iommu_capability_write(struct file *filp, const char __user *ubuf,
>> + size_t cnt, loff_t *ppos)
>> +{
>> + int ret;
>> +
>> + if (cnt > OFS_IN_SZ)
>> + return -EINVAL;
>> +
>> + ret = kstrtou32_from_user(ubuf, cnt, 0, &cap_offset);
>> + if (ret)
>> + return ret;
>> +
>> + /* Capability register at offset 0x14 is the last IOMMU capability register. */
>> + if (cap_offset > 0x14) {
>> + cap_offset = -1;
>> + return -EINVAL;
>> + }
>> +
>> + return cnt;
>> +}
>> +
>> +static int iommu_capability_show(struct seq_file *m, void *unused)
>> +{
>> + struct amd_iommu *iommu = m->private;
>> + u32 value;
>> + int err;
>> +
>> + if (cap_offset < 0) {
>> + seq_puts(m, "Please provide capability register's offset\n");
>
> May be you can add last offset details... so that it becomes easy to find out
> the offset range.
Sure.
Thanks
Dheeraj
>
> -Vasant
>
>
next prev parent reply other threads:[~2025-03-17 11:23 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 [this message]
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
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=3c14597f-e5dd-4e43-bd4a-6f7a6d08afa7@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