From: "Somalapuram, Amaranath" <asomalap@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
"Somalapuram Amaranath" <Amaranath.Somalapuram@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, shashank.sharma@amd.com
Subject: Re: [PATCH v4 1/2] drm/amdgpu: add debugfs for reset registers list
Date: Tue, 15 Feb 2022 16:45:16 +0530 [thread overview]
Message-ID: <7e09e7e2-3f04-ebb9-7654-95cc0e54dda7@amd.com> (raw)
In-Reply-To: <e678e107-530e-260d-b14e-f742a651859e@amd.com>
On 2/15/2022 3:46 PM, Christian König wrote:
>
>
> Am 15.02.22 um 11:12 schrieb Somalapuram Amaranath:
>> List of register populated for dump collection during the GPU reset.
>>
>> Signed-off-by: Somalapuram Amaranath <Amaranath.Somalapuram@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 4 +
>> drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 89 +++++++++++++++++++++
>> 2 files changed, 93 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> index b85b67a88a3d..2e8c2318276d 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> @@ -1097,6 +1097,10 @@ struct amdgpu_device {
>> struct amdgpu_reset_control *reset_cntl;
>> uint32_t ip_versions[HW_ID_MAX][HWIP_MAX_INSTANCE];
>> +
>> + /* reset dump register */
>> + uint32_t *reset_dump_reg_list;
>> + int n_regs;
>> };
>> static inline struct amdgpu_device *drm_to_adev(struct drm_device
>> *ddev)
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> index 164d6a9e9fbb..edcb032bc1f3 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
>> @@ -1609,6 +1609,93 @@ DEFINE_DEBUGFS_ATTRIBUTE(fops_ib_preempt, NULL,
>> DEFINE_DEBUGFS_ATTRIBUTE(fops_sclk_set, NULL,
>> amdgpu_debugfs_sclk_set, "%llu\n");
>> +static ssize_t amdgpu_reset_dump_register_list_read(struct file *f,
>> + char __user *buf, size_t size, loff_t *pos)
>> +{
>> + struct amdgpu_device *adev = (struct amdgpu_device
>> *)file_inode(f)->i_private;
>> + char reg_offset[11];
>> + int i, r, len = 0;
>> +
>> + if (adev->n_regs == 0)
>> + return 0;
>> +
>> + for (i = 0; i < adev->n_regs; i++) {
>> + memset(reg_offset, 0, 11);
>> + sprintf(reg_offset + strlen(reg_offset),
>
> That here looks odd, probably just a leftover from the older code.
>
My mistake leftover code.
let me try to remove memset() also.
> Without it you can also drop the memset().
>
>> + "0x%x ", adev->reset_dump_reg_list[i]);
>> + r = copy_to_user(buf + len, reg_offset, strlen(reg_offset));
>
> Whenever copy_to_user() returns a nonzero value the best practice is
> to return -EFAULT.
>
agreed.
>> + len += strlen(reg_offset);
>> + }
>> +
>> + r = copy_to_user(buf + len, "\n", 1);
>
> Same here.
>
agreed.
>> + len++;
>> +
>> + if (*pos >= len)
>> + return 0;
>
> What is that good for?
>
If i don't have this condition read operation will be infinite loop and
data keeps repeating.
I am not sure why !. maybe i need to set something while write operation.
> Regards,
> Christian.
>
>> +
>> + *pos += len - r;
>> +
>> + return len;
>> +}
>> +
>> +static ssize_t amdgpu_reset_dump_register_list_write(struct file *f,
>> + const char __user *buf, size_t size, loff_t *pos)
>> +{
>> + struct amdgpu_device *adev = (struct amdgpu_device
>> *)file_inode(f)->i_private;
>> + char *reg_offset, *reg, reg_temp[11];
>> + int ret, i = 0, len = 0;
>> +
>> + reg_offset = reg_temp;
>> + memset(reg_offset, 0, 11);
>> + ret = copy_from_user(reg_offset, buf, 11);
>> +
>> + if (ret)
>> + return -EFAULT;
>> +
>> + if (adev->n_regs > 0) {
>> + adev->n_regs = 0;
>> + kfree(adev->reset_dump_reg_list);
>> + adev->reset_dump_reg_list = NULL;
>> + }
>> +
>> + while (((reg = strsep(®_offset, " ")) != NULL) && len < size) {
>> + adev->reset_dump_reg_list = krealloc_array(
>> + adev->reset_dump_reg_list, 1,
>> + sizeof(uint32_t), GFP_KERNEL);
>> + ret = kstrtouint(reg, 16, &adev->reset_dump_reg_list[i]);
>> +
>> + if (ret) {
>> + kfree(adev->reset_dump_reg_list);
>> + adev->reset_dump_reg_list = NULL;
>> + return -EINVAL;
>> + }
>> +
>> + len += strlen(reg) + 1;
>> + reg_offset = reg_temp;
>> + memset(reg_offset, 0, 11);
>> + ret = copy_from_user(reg_offset, buf + len, 11);
>> +
>> + if (ret) {
>> + kfree(adev->reset_dump_reg_list);
>> + adev->reset_dump_reg_list = NULL;
>> + return -EFAULT;
>> + }
>> +
>> + i++;
>> + }
>> +
>> + adev->n_regs = i;
>> +
>> + return size;
>> +}
>> +
>> +static const struct file_operations amdgpu_reset_dump_register_list = {
>> + .owner = THIS_MODULE,
>> + .read = amdgpu_reset_dump_register_list_read,
>> + .write = amdgpu_reset_dump_register_list_write,
>> + .llseek = default_llseek
>> +};
>> +
>> int amdgpu_debugfs_init(struct amdgpu_device *adev)
>> {
>> struct dentry *root = adev_to_drm(adev)->primary->debugfs_root;
>> @@ -1672,6 +1759,8 @@ int amdgpu_debugfs_init(struct amdgpu_device
>> *adev)
>> &amdgpu_debugfs_test_ib_fops);
>> debugfs_create_file("amdgpu_vm_info", 0444, root, adev,
>> &amdgpu_debugfs_vm_info_fops);
>> + debugfs_create_file("amdgpu_reset_dump_register_list", 0644,
>> root, adev,
>> + &amdgpu_reset_dump_register_list);
>> adev->debugfs_vbios_blob.data = adev->bios;
>> adev->debugfs_vbios_blob.size = adev->bios_size;
>
prev parent reply other threads:[~2022-02-15 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 10:12 [PATCH v4 1/2] drm/amdgpu: add debugfs for reset registers list Somalapuram Amaranath
2022-02-15 10:12 ` [PATCH v4 2/2] drm/amdgpu: add reset register dump trace on GPU reset Somalapuram Amaranath
2022-02-15 16:39 ` Andrey Grodzovsky
2022-02-16 10:46 ` Somalapuram, Amaranath
2022-02-16 15:40 ` Andrey Grodzovsky
2022-02-15 10:16 ` [PATCH v4 1/2] drm/amdgpu: add debugfs for reset registers list Christian König
2022-02-15 11:15 ` Somalapuram, Amaranath [this message]
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=7e09e7e2-3f04-ebb9-7654-95cc0e54dda7@amd.com \
--to=asomalap@amd.com \
--cc=Amaranath.Somalapuram@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=shashank.sharma@amd.com \
/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