From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Evan Quan <evan.quan@amd.com>, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, hawking.zhang@amd.com
Subject: Re: [PATCH 1/2] drm/amdgpu: drop non-necessary call trace dump
Date: Wed, 20 Jul 2022 14:50:18 +0200 [thread overview]
Message-ID: <ee4e323a-38c6-208c-417b-d3101aeee067@gmail.com> (raw)
In-Reply-To: <20220720090640.47497-1-evan.quan@amd.com>
Am 20.07.22 um 11:06 schrieb Evan Quan:
> This extra call trace dump comes out in every gpu reset.
> And it gives people a wrong impression that something
> went wrong. Although actually there was not.
>
> Signed-off-by: Evan Quan <evan.quan@amd.com>
> Change-Id: I884af405b6b3cd52b9024408a21fd39811a01f4d
Acked-by: Christian König <christian.koenig@amd.com>
And please guys don't add calls to dump_stack() in the future. That's
really not supposed to be here.
Thanks,
Christian.
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index b79ee4ffb879..1b1a70a6da18 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -4667,7 +4667,6 @@ static int amdgpu_reset_reg_dumps(struct amdgpu_device *adev)
> int i;
>
> lockdep_assert_held(&adev->reset_domain->sem);
> - dump_stack();
>
> for (i = 0; i < adev->num_regs; i++) {
> adev->reset_dump_reg_value[i] = RREG32(adev->reset_dump_reg_list[i]);
prev parent reply other threads:[~2022-07-20 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 9:06 [PATCH 1/2] drm/amdgpu: drop non-necessary call trace dump Evan Quan
2022-07-20 9:06 ` [PATCH 2/2] drm/amdgpu: move mes self test after drm sched re-started Evan Quan
2022-07-20 12:50 ` Christian König [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=ee4e323a-38c6-208c-417b-d3101aeee067@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=evan.quan@amd.com \
--cc=hawking.zhang@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