AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: "Christian König" <christian.koenig@amd.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org,
	"Philipp Stanner" <phasta@kernel.org>
Cc: Jesse Zhang <jesse.zhang@amd.com>
Subject: Re: [PATCH 01/12] drm/amdgpu: re-add the bad job to the pending list for ring resets
Date: Fri, 30 Jan 2026 16:43:54 +0100	[thread overview]
Message-ID: <9b307a300bf7ece290339f78805b7ee0c1420dea.camel@mailbox.org> (raw)
In-Reply-To: <e8bbdbef-8d34-4465-9ad1-aead5e1f9361@amd.com>

On Fri, 2026-01-30 at 16:30 +0100, Christian König wrote:
> 
> 
> On 1/29/26 21:37, Alex Deucher wrote:
> > Need to re-add the bad job to the pending list before we
> > restart the scheduler.
> > 
> > Reviewed-by: Jesse Zhang <jesse.zhang@amd.com>
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> > ---
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_job.c  | 6 ++++++
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c | 4 ----
> >  2 files changed, 6 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
> > index aaf5477fcd7ac..9b10470321be3 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
> > @@ -135,8 +135,14 @@ static enum drm_gpu_sched_stat amdgpu_job_timedout(struct drm_sched_job *s_job)
> >  	    ring->funcs->reset) {
> >  		dev_err(adev->dev, "Starting %s ring reset\n",
> >  			s_job->sched->name);
> > +		/* Stop the scheduler to prevent anybody else from touching the ring buffer. */
> > +		drm_sched_wqueue_stop(&ring->sched);
> >  		r = amdgpu_ring_reset(ring, job->vmid, job->hw_fence);
> >  		if (!r) {
> > +			/* add the job back to the pending list */
> > +			list_add(&s_job->list, &s_job->sched->pending_list);
> 
> This is explicitly forbidden by the scheduler maintainer.

Fun fact: In English they sometimes use our german word "verboten" :)

> 
> So we seriously can't do that here.
> 
> Correct approach would be to return the proper code to the scheduler so that the scheduler does that.

Yes.
Thank you very much, Christian.

Layering violations and ossification of API internals is one of the
main reasons that brought drm_sched to the brink of unmaintainability.
I think I was very explicit about this at XDC.

Our friends at AMD shall take Panfrost as an inspiration:
https://elixir.bootlin.com/linux/v6.19-rc4/source/drivers/gpu/drm/panfrost/panfrost_job.c#L760


P.

> 
> Regards,
> Christian.
> 
> > +			/* Start the scheduler again */
> > +			drm_sched_wqueue_start(&ring->sched);
> >  			atomic_inc(&ring->adev->gpu_reset_counter);
> >  			dev_err(adev->dev, "Ring %s reset succeeded\n",
> >  				ring->sched.name);
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> > index b82357c657237..129ad51386535 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ring.c
> > @@ -868,8 +868,6 @@ bool amdgpu_ring_sched_ready(struct amdgpu_ring *ring)
> >  void amdgpu_ring_reset_helper_begin(struct amdgpu_ring *ring,
> >  				    struct amdgpu_fence *guilty_fence)
> >  {
> > -	/* Stop the scheduler to prevent anybody else from touching the ring buffer. */
> > -	drm_sched_wqueue_stop(&ring->sched);
> >  	/* back up the non-guilty commands */
> >  	amdgpu_ring_backup_unprocessed_commands(ring, guilty_fence);
> >  }
> > @@ -895,8 +893,6 @@ int amdgpu_ring_reset_helper_end(struct amdgpu_ring *ring,
> >  			amdgpu_ring_write(ring, ring->ring_backup[i]);
> >  		amdgpu_ring_commit(ring);
> >  	}
> > -	/* Start the scheduler again */
> > -	drm_sched_wqueue_start(&ring->sched);
> >  	return 0;
> >  }
> >  
> 


  reply	other threads:[~2026-02-01 10:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 20:37 [PATCH 00/12] Improvements for IB handling V7 Alex Deucher
2026-01-29 20:37 ` [PATCH 01/12] drm/amdgpu: re-add the bad job to the pending list for ring resets Alex Deucher
2026-01-30 15:30   ` Christian König
2026-01-30 15:43     ` Philipp Stanner [this message]
2026-01-30 16:25     ` Alex Deucher
2026-01-29 20:37 ` [PATCH 02/12] drm/amdgpu/job: use GFP_ATOMIC while in gpu reset Alex Deucher
2026-01-29 20:37 ` [PATCH 03/12] drm/amdgpu: switch all IPs to using job for IBs Alex Deucher
2026-01-29 20:37 ` [PATCH 04/12] drm/amdgpu: require a job to schedule an IB Alex Deucher
2026-01-29 20:37 ` [PATCH 05/12] drm/amdgpu: don't call drm_sched_stop/start() in asic reset Alex Deucher
2026-01-29 20:37 ` [PATCH 06/12] drm/amdgpu/cs: return -ETIME for guilty contexts Alex Deucher
2026-01-29 20:37 ` [PATCH 07/12] drm/amdgpu: plumb timedout fence through to force completion Alex Deucher
2026-01-29 20:37 ` [PATCH 08/12] drm/amdgpu: simplify VCN reset helper Alex Deucher
2026-01-29 20:37 ` [PATCH 09/12] drm/amdgpu: Call drm_sched_increase_karma() for ring resets Alex Deucher
2026-01-29 20:37 ` [PATCH 10/12] drm/amdgpu: reorder IB schedule sequence Alex Deucher
2026-01-29 20:37 ` [PATCH 11/12] drm/amdgpu: add a helper to calculate ring distance Alex Deucher
2026-01-29 20:37 ` [PATCH 12/12] drm/amdgpu: rework ring reset backup and reemit v8 Alex Deucher
  -- strict thread matches above, loose matches on Subject: below --
2026-01-30 17:30 [PATCH 00/12] Improvements for IB handling V8 Alex Deucher
2026-01-30 17:30 ` [PATCH 01/12] drm/amdgpu: re-add the bad job to the pending list for ring resets Alex Deucher
2026-02-05 13:34   ` Pierre-Eric Pelloux-Prayer

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=9b307a300bf7ece290339f78805b7ee0c1420dea.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=jesse.zhang@amd.com \
    --cc=phasta@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