All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Alex Deucher" <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH] drm/amdgpu: always emit the job vm fence
Date: Fri, 05 Jun 2026 12:11:04 +0200	[thread overview]
Message-ID: <5051245.OV4Wx5bFTl@timur-max> (raw)
In-Reply-To: <9cc1c11a-ffbd-4b33-9608-111ba12bed1d@amd.com>

On 2026. június 5., péntek 11:24:45 közép-európai nyári idő Christian König 
wrote:
> On 6/3/26 21:45, Alex Deucher wrote:
> > We need the fence to reemit the gds switch or spm update
> > after a queue reset.
> > 
> > Fixes: a17ef941212b ("drm/amdgpu: rework ring reset backup and reemit v9")
> > Cc: timur.kristof@gmail.com
> > Cc: christian.koenig@amd.com
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> 
> That was avoided because it means another entry in the EOP ring buffer which
> can be bad for performance.
> 
> But correctness is obviously more important, just to keep in mind when we
> suddenly see 1% fps decrease and don't know where it's coming from.
> 
> Reviewed-by: Christian König <christian.koenig@amd.com>

Thanks Christian, that's a valid point.
Do you think we should worry about an actual perf impact here?

If we want to avoid adding an extra fence, then an alternative solution could 
be to include the emitted commands in the ib_wptr of the job's own fence when 
a VM fence was not emitted.

What do you guys think?

Thanks,
Timur

> 
> > ---
> > 
> >  drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> > b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index
> > 2f3470208829e..7e0e2281719b1 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> > @@ -853,12 +853,10 @@ void amdgpu_vm_flush(struct amdgpu_ring *ring,
> > struct amdgpu_job *job,> 
> >  					    job->oa_size);
> >  	
> >  	}
> > 
> > -	if (vm_flush_needed || pasid_mapping_needed || 
cleaner_shader_needed) {
> > -		amdgpu_fence_emit(ring, job->hw_vm_fence, 0);
> > -		fence = &job->hw_vm_fence->base;
> > -		/* get a ref for the job */
> > -		dma_fence_get(fence);
> > -	}
> > +	amdgpu_fence_emit(ring, job->hw_vm_fence, 0);
> > +	fence = &job->hw_vm_fence->base;
> > +	/* get a ref for the job */
> > +	dma_fence_get(fence);
> > 
> >  	if (vm_flush_needed) {
> >  	
> >  		mutex_lock(&id_mgr->lock);





  reply	other threads:[~2026-06-05 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 19:45 [PATCH] drm/amdgpu: always emit the job vm fence Alex Deucher
2026-06-04 11:06 ` Timur Kristóf
2026-06-05  9:24 ` Christian König
2026-06-05 10:11   ` Timur Kristóf [this message]
2026-06-05 22:19     ` Alex Deucher

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=5051245.OV4Wx5bFTl@timur-max \
    --to=timur.kristof@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.