public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Friedrich Vock" <friedrich.vock@gmx.de>,
	"Christian König" <christian.koenig@amd.com>,
	"Joshua Ashton" <joshua@froggi.es>,
	amd-gfx@lists.freedesktop.org, "Olsak,
	Marek" <Marek.Olsak@amd.com>
Cc: "Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>,
	"André Almeida" <andrealmeid@igalia.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/3] drm/amdgpu: Forward soft recovery errors to userspace
Date: Fri, 2 Aug 2024 10:30:08 +0200	[thread overview]
Message-ID: <c600abec-d16b-45d3-afe3-f10ba2fc8871@gmail.com> (raw)
In-Reply-To: <641ce39c-a6a6-4448-bb2a-9c12d2873c1c@gmx.de>

Am 01.08.24 um 17:17 schrieb Friedrich Vock:
> Hi,
>
> I happened to come across an issue just now again where soft recovery
> fails to get reported to userspace properly, causing apps to submit
> hanging work in a loop (which ended up hanging the entire machine) - it
> seems like this patch never made it into amd-staging-drm-next. Given
> that it has a Reviewed-by and everything, was this just an oversight or
> are there some blockers to pushing it that I missed?
>
> If not, I'd be grateful if the patch could get merged.

Sorry that was my fault, I've forgotten about it because Alex usually 
picks up stuff for amd-staging-drm-next.

Thanks for the reminder, just pushed it.

Regards,
Christian.

>
> Thanks,
> Friedrich
>
> On 08.03.24 09:33, Christian König wrote:
>> Am 07.03.24 um 20:04 schrieb Joshua Ashton:
>>> As we discussed before[1], soft recovery should be
>>> forwarded to userspace, or we can get into a really
>>> bad state where apps will keep submitting hanging
>>> command buffers cascading us to a hard reset.
>>
>> Marek you are in favor of this like forever.  So I would like to request
>> you to put your Reviewed-by on it and I will just push it into our
>> internal kernel branch.
>>
>> Regards,
>> Christian.
>>
>>>
>>> 1:
>>> https://lore.kernel.org/all/bf23d5ed-9a6b-43e7-84ee-8cbfd0d60f18@froggi.es/ 
>>>
>>> Signed-off-by: Joshua Ashton <joshua@froggi.es>
>>>
>>> Cc: Friedrich Vock <friedrich.vock@gmx.de>
>>> Cc: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
>>> Cc: Christian König <christian.koenig@amd.com>
>>> Cc: André Almeida <andrealmeid@igalia.com>
>>> Cc: stable@vger.kernel.org
>>> ---
>>>   drivers/gpu/drm/amd/amdgpu/amdgpu_job.c | 3 +--
>>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
>>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
>>> index 4b3000c21ef2..aebf59855e9f 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
>>> @@ -262,9 +262,8 @@ amdgpu_job_prepare_job(struct drm_sched_job
>>> *sched_job,
>>>       struct dma_fence *fence = NULL;
>>>       int r;
>>> -    /* Ignore soft recovered fences here */
>>>       r = drm_sched_entity_error(s_entity);
>>> -    if (r && r != -ENODATA)
>>> +    if (r)
>>>           goto error;
>>>       if (!fence && job->gang_submit)
>>


      reply	other threads:[~2024-08-02  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 19:04 [PATCH 1/3] drm/amdgpu: Forward soft recovery errors to userspace Joshua Ashton
2024-03-07 19:04 ` [PATCH 2/3] drm/amdgpu: Determine soft recovery deadline next to usage Joshua Ashton
2024-03-08  8:23   ` Christian König
2024-03-07 19:04 ` [PATCH 3/3] drm/amdgpu: Increase soft recovery timeout to .5s Joshua Ashton
2024-03-08  8:29   ` Christian König
2024-03-08 22:31     ` Joshua Ashton
2024-03-11  6:46       ` Christian König
2024-03-08  8:33 ` [PATCH 1/3] drm/amdgpu: Forward soft recovery errors to userspace Christian König
2024-03-09 16:27   ` Marek Olšák
2024-08-01 15:17   ` Friedrich Vock
2024-08-02  8:30     ` 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=c600abec-d16b-45d3-afe3-f10ba2fc8871@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=Marek.Olsak@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrealmeid@igalia.com \
    --cc=bas@basnieuwenhuizen.nl \
    --cc=christian.koenig@amd.com \
    --cc=friedrich.vock@gmx.de \
    --cc=joshua@froggi.es \
    --cc=stable@vger.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