From: "Christian König" <christian.koenig@amd.com>
To: "André Almeida" <andrealmeid@igalia.com>,
"Raag Jadav" <raag.jadav@intel.com>,
airlied@gmail.com, simona@ffwll.ch, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com, lina@asahilina.net,
michal.wajdeczko@intel.com, "Sharma,
Shashank" <Shashank.Sharma@amd.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
himal.prasad.ghimiray@intel.com,
aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com,
alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
kernel-dev@igalia.com
Subject: Re: [PATCH 1/1] drm/amdgpu: Use device wedged event
Date: Fri, 13 Dec 2024 08:34:18 +0100 [thread overview]
Message-ID: <d9f2583d-da79-4532-90fc-85028e977ceb@amd.com> (raw)
In-Reply-To: <20241212190909.28559-2-andrealmeid@igalia.com>
Am 12.12.24 um 20:09 schrieb André Almeida:
> Use DRM's device wedged event to notify userspace that a reset had
> happened. For now, only use `none` method meant for telemetry
> capture.
>
> Signed-off-by: André Almeida <andrealmeid@igalia.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 96316111300a..19e1a5493778 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -6057,6 +6057,9 @@ int amdgpu_device_gpu_recover(struct amdgpu_device *adev,
> dev_info(adev->dev, "GPU reset end with ret = %d\n", r);
>
> atomic_set(&adev->reset_domain->reset_res, r);
> +
> + drm_dev_wedged_event(adev_to_drm(adev), DRM_WEDGE_RECOVERY_NONE);
That looks really good in general. I would just make the
DRM_WEDGE_RECOVERY_NONE depend on the value of "r".
@Shashank any objections? IIRC you have worked on the AMD specific event
we never upstreamed.
Regards,
Christian.
> +
> return r;
> }
>
next prev parent reply other threads:[~2024-12-13 7:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 19:09 [PATCH 0/1] drm/amdgpu: Use device wedged event André Almeida
2024-12-12 19:09 ` [PATCH 1/1] " André Almeida
2024-12-13 7:34 ` Christian König [this message]
2024-12-13 7:46 ` Sharma, Shashank
2024-12-13 14:15 ` André Almeida
2024-12-13 14:36 ` Raag Jadav
2024-12-13 15:56 ` André Almeida
2024-12-16 10:18 ` Christian König
2024-12-16 10:38 ` Lazar, Lijo
2024-12-16 13:04 ` André Almeida
2024-12-16 13:10 ` Christian König
2024-12-16 13:15 ` André Almeida
2024-12-16 13:36 ` Christian König
2024-12-16 13:36 ` Lazar, Lijo
2024-12-16 13:39 ` Christian König
2024-12-16 13:44 ` Lazar, Lijo
2024-12-16 13:57 ` Raag Jadav
2024-12-20 13:31 ` kernel test robot
2024-12-20 14:06 ` kernel test robot
2024-12-13 14:10 ` [PATCH 0/1] " Lucas De Marchi
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=d9f2583d-da79-4532-90fc-85028e977ceb@amd.com \
--to=christian.koenig@amd.com \
--cc=Shashank.Sharma@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=lina@asahilina.net \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
/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