From: "André Almeida" <andrealmeid@igalia.com>
To: Shashank Sharma <shashank.sharma@amd.com>
Cc: pierre-eric.pelloux-prayer@amd.com,
amd-gfx@lists.freedesktop.org, "'Marek Olšák'" <maraeo@gmail.com>,
"Timur Kristóf" <timur.kristof@gmail.com>,
"Samuel Pitoiset" <samuel.pitoiset@gmail.com>,
kernel-dev@igalia.com, alexander.deucher@amd.com,
christian.koenig@amd.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4 2/4] drm/amdgpu: Rework coredump to use memory dynamically
Date: Thu, 17 Aug 2023 10:45:30 -0300 [thread overview]
Message-ID: <a6e90991-91bb-4da9-ab67-d0ec28a29680@igalia.com> (raw)
In-Reply-To: <07ef59db-da17-15cf-789a-7f5d01b2c9c9@amd.com>
Hi Shashank,
Em 17/08/2023 03:41, Shashank Sharma escreveu:
> Hello Andre,
>
> On 15/08/2023 21:50, André Almeida wrote:
>> Instead of storing coredump information inside amdgpu_device struct,
>> move if to a proper separated struct and allocate it dynamically. This
>> will make it easier to further expand the logged information.
>>
>> Signed-off-by: André Almeida <andrealmeid@igalia.com>
>> ---
>> v4: change kmalloc to kzalloc
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 14 +++--
>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 63 ++++++++++++++--------
>> 2 files changed, 49 insertions(+), 28 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> index 9c6a332261ab..0d560b713948 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>> @@ -1088,11 +1088,6 @@ struct amdgpu_device {
>> uint32_t *reset_dump_reg_list;
>> uint32_t *reset_dump_reg_value;
>> int num_regs;
>> -#ifdef CONFIG_DEV_COREDUMP
>> - struct amdgpu_task_info reset_task_info;
>> - bool reset_vram_lost;
>> - struct timespec64 reset_time;
>> -#endif
>> bool scpm_enabled;
>> uint32_t scpm_status;
>> @@ -1105,6 +1100,15 @@ struct amdgpu_device {
>> uint32_t aid_mask;
>> };
>> +#ifdef CONFIG_DEV_COREDUMP
>> +struct amdgpu_coredump_info {
>> + struct amdgpu_device *adev;
>> + struct amdgpu_task_info reset_task_info;
>> + struct timespec64 reset_time;
>> + bool reset_vram_lost;
>> +};
>
> The patch looks good to me in general, but I would recommend slightly
> different arrangement and segregation of GPU reset information.
>
> Please consider a higher level structure adev->gpu_reset_info, and move
> everything related to reset dump info into that, including this new
> coredump_info structure, something like this:
>
> struct amdgpu_reset_info {
>
> uint32_t *reset_dump_reg_list;
>
> uint32_t *reset_dump_reg_value;
>
> int num_regs;
>
Right, I can encapsulate there reset_dump members,
> #ifdef CONFIG_DEV_COREDUMP
>
> struct amdgpu_coredump_info *coredump_info;/* keep this dynamic
> allocation */
but we don't need a pointer for amdgpu_coredump_info inside
amdgpu_device or inside of amdgpu_device->gpu_reset_info, right?
>
> #endif
>
> }
>
>
> This will make sure that all the relevant information is at the same place.
>
> - Shashank
>
amdgpu_inc_vram_lost(tmp_adev);
next prev parent reply other threads:[~2023-08-17 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 19:50 [PATCH v4 0/4] drm/amdgpu: Rework coredump memory allocation André Almeida
2023-08-15 19:50 ` [PATCH v4 1/4] drm/amdgpu: Allocate coredump memory in a nonblocking way André Almeida
2023-08-15 19:50 ` [PATCH v4 2/4] drm/amdgpu: Rework coredump to use memory dynamically André Almeida
2023-08-16 9:48 ` Christian König
2023-08-16 10:11 ` Shashank Sharma
2023-08-17 6:41 ` Shashank Sharma
2023-08-17 13:45 ` André Almeida [this message]
2023-08-17 15:04 ` Shashank Sharma
2023-08-17 15:17 ` André Almeida
2023-08-17 15:26 ` Shashank Sharma
2023-08-17 15:38 ` André Almeida
2023-08-17 15:42 ` Shashank Sharma
2023-08-15 19:50 ` [PATCH v4 3/4] drm/amdgpu: Move coredump code to amdgpu_reset file André Almeida
2023-08-16 9:52 ` Christian König
2023-08-15 19:51 ` [PATCH v4 4/4] drm/amdgpu: Create version number for coredumps André Almeida
2023-08-16 9:50 ` Christian König
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=a6e90991-91bb-4da9-ab67-d0ec28a29680@igalia.com \
--to=andrealmeid@igalia.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maraeo@gmail.com \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=samuel.pitoiset@gmail.com \
--cc=shashank.sharma@amd.com \
--cc=timur.kristof@gmail.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
all inboxes | Powered by JetHome®