Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "Brost, Matthew" <matthew.brost@intel.com>,
	"Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"Harrison, John C" <john.c.harrison@intel.com>,
	"Vishwanathapura,
	Niranjana" <niranjana.vishwanathapura@intel.com>,
	"Gupta, saurabhg" <saurabhg.gupta@intel.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Welty, Brian" <brian.welty@intel.com>
Subject: Re: [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function definitions
Date: Mon, 15 Apr 2024 22:23:49 +0000	[thread overview]
Message-ID: <ac576c169912f5f6663a38b1c273e7ef84122ae6.camel@intel.com> (raw)
In-Reply-To: <CH0PR11MB54440A904094FD4CFC89749AE5092@CH0PR11MB5444.namprd11.prod.outlook.com>

On Mon, 2024-04-15 at 20:41 +0000, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Brost, Matthew <matthew.brost@intel.com> 
> Sent: Monday, April 15, 2024 1:29 PM
> To: Cavitt, Jonathan <jonathan.cavitt@intel.com>
> Cc: Summers, Stuart <stuart.summers@intel.com>;
> intel-xe@lists.freedesktop.org; Harrison, John C
> <john.c.harrison@intel.com>; Vishwanathapura, Niranjana
> <niranjana.vishwanathapura@intel.com>; Gupta, saurabhg
> <saurabhg.gupta@intel.com>; Roper, Matthew D
> <matthew.d.roper@intel.com>; Welty, Brian <brian.welty@intel.com>
> Subject: Re: [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function
> definitions
> > 
> > On Mon, Apr 15, 2024 at 02:26:38PM -0600, Cavitt, Jonathan wrote:
> > > -----Original Message-----
> > > From: Brost, Matthew <matthew.brost@intel.com> 
> > > Sent: Monday, April 15, 2024 12:44 PM
> > > To: Summers, Stuart <stuart.summers@intel.com>
> > > Cc: intel-xe@lists.freedesktop.org; Cavitt, Jonathan
> > > <jonathan.cavitt@intel.com>; Harrison, John C
> > > <john.c.harrison@intel.com>; Vishwanathapura, Niranjana
> > > <niranjana.vishwanathapura@intel.com>; Gupta, saurabhg
> > > <saurabhg.gupta@intel.com>; Roper, Matthew D
> > > <matthew.d.roper@intel.com>; Welty, Brian <brian.welty@intel.com>
> > > Subject: Re: [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail
> > > function definitions
> > > > 
> > > > On Mon, Apr 15, 2024 at 01:31:32PM -0600, Summers, Stuart
> > > > wrote:
> > > > > On Mon, 2024-04-15 at 11:46 -0700, Jonathan Cavitt wrote:
> > > > > > Add defintions for the functions xe_lrc_set_ring_tail and
> > > > > > xe_lrc_ring_tail to match the definitions for
> > > > > > xe_lrc_set_ring_head
> > > > > > and
> > > > > > xe_lrc_ring_head, respectively, except tarting the lrc
> > > > > > tail.
> > > > > > 
> > > > > > Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> > > > > > CC: Niranjana Vishwanathapura
> > > > > > <niranjana.vishwanathapura@intel.com>
> > > > > > CC: Brian Welty <brian.welty@intel.com>
> > > > > > CC: Matt Roper <matthew.d.roper@intel.com>
> > > > > > ---
> > > > > >  drivers/gpu/drm/xe/xe_lrc.c | 10 ++++++++++
> > > > > >  drivers/gpu/drm/xe/xe_lrc.h |  2 ++
> > > > > >  2 files changed, 12 insertions(+)
> > > > > > 
> > > > > > diff --git a/drivers/gpu/drm/xe/xe_lrc.c
> > > > > > b/drivers/gpu/drm/xe/xe_lrc.c
> > > > > > index 615bbc372ac62..e91ecbcceba5c 100644
> > > > > > --- a/drivers/gpu/drm/xe/xe_lrc.c
> > > > > > +++ b/drivers/gpu/drm/xe/xe_lrc.c
> > > > > > @@ -834,6 +834,16 @@ void xe_lrc_finish(struct xe_lrc *lrc)
> > > > > >         xe_bo_put(lrc->bo);
> > > > > >  }
> > > > > >  
> > > > > > +void xe_lrc_set_ring_tail(struct xe_lrc *lrc, u32 tail)
> > > > > > +{
> > > > > > +       xe_lrc_write_ctx_reg(lrc, CTX_RING_TAIL, tail);
> > > > > > +}
> > > > > > +
> > > > > > +u32 xe_lrc_ring_tail(struct xe_lrc *lrc)
> > > > > > +{
> > > > > > +       return xe_lrc_read_ctx_reg(lrc, CTX_RING_TAIL) &
> > > > > > TAIL_ADDR;
> > > > > > +}
> > > > > > +
> > > > > >  void xe_lrc_set_ring_head(struct xe_lrc *lrc, u32 head)
> > > > > >  {
> > > > > 
> > > > > I see lower in xe_lrc.c we're doing this
> > > > > (xe_lrc_snapshot_capture):
> > > > > snapshot->tail.memory = xe_lrc_read_ctx_reg(lrc,
> > > > > CTX_RING_TAIL);
> > > > > 
> > > > > Should we change this call to use the new wrapper also?
> > > > > 
> > > > 
> > > > Yea. Also xe_guc_submit.c sets the LRC tail. It should be
> > > > updated to use
> > > > the helper too.
> > > 
> > > Please list all of the places where you would like me to use
> > > xe_lrc_set_ring_tail
> > > and xe_lrc_ring_tail, and I will have those ready for the next
> > > revision.
> > > -Jonathan Cavitt
> > > 
> > 
> > grep is your friend...
> > 
> > mbrost@lstrano-desk:xe$ grep CTX_RING_TAIL *.c *.h
> > xe_execlist.c:  xe_lrc_write_ctx_reg(lrc, CTX_RING_TAIL, lrc-
> > >ring.tail);
> > xe_guc_submit.c:                xe_lrc_write_ctx_reg(lrc,
> > CTX_RING_TAIL, lrc->ring.tail);
> > xe_lrc.c:       xe_lrc_write_ctx_reg(lrc, CTX_RING_TAIL, lrc-
> > >ring.tail);
> > xe_lrc.c:       snapshot->tail.memory = xe_lrc_read_ctx_reg(lrc,
> > CTX_RING_TAIL);
> 
> And in the snapshot case, we're sure we want to use xe_lrc_ring_tail
> instead of
> the current raw call?  Because xe_lrc_ring_tail performs a bitwise
> AND on the
> result, which we might not want.
> Granted, I don't know why we wouldn't want it, but that's still a
> point of contention
> that may come up in post-review.

Honestly to me the AND there is actually making this more accurate for
the snapshot anyway - something we probably should add anyway there.
I'd suggest using the same routine everywhere.

Thanks,
Stuart

> -Jonathan Cavitt
> 
> > 
> > Matt
> > 
> > > > 
> > > > Matt
> > > > 
> > > > > Thanks,
> > > > > Stuart
> > > > > 
> > > > > >         xe_lrc_write_ctx_reg(lrc, CTX_RING_HEAD, head);
> > > > > > diff --git a/drivers/gpu/drm/xe/xe_lrc.h
> > > > > > b/drivers/gpu/drm/xe/xe_lrc.h
> > > > > > index d32fa31faa2cf..f355b0eeb5658 100644
> > > > > > --- a/drivers/gpu/drm/xe/xe_lrc.h
> > > > > > +++ b/drivers/gpu/drm/xe/xe_lrc.h
> > > > > > @@ -24,6 +24,8 @@ void xe_lrc_finish(struct xe_lrc *lrc);
> > > > > >  size_t xe_lrc_size(struct xe_device *xe, enum
> > > > > > xe_engine_class
> > > > > > class);
> > > > > >  u32 xe_lrc_pphwsp_offset(struct xe_lrc *lrc);
> > > > > >  
> > > > > > +void xe_lrc_set_ring_tail(struct xe_lrc *lrc, u32 tail);
> > > > > > +u32 xe_lrc_ring_tail(struct xe_lrc *lrc);
> > > > > >  void xe_lrc_set_ring_head(struct xe_lrc *lrc, u32 head);
> > > > > >  u32 xe_lrc_ring_head(struct xe_lrc *lrc);
> > > > > >  u32 xe_lrc_ring_space(struct xe_lrc *lrc);
> > > > > 
> > > > 
> > 


  reply	other threads:[~2024-04-15 22:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 18:46 [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function definitions Jonathan Cavitt
2024-04-15 18:46 ` [PATCH v5 2/4] drm/xe/xe_guc_submit: Fix exec queue stop race condition Jonathan Cavitt
2024-04-15 18:46 ` [PATCH v5 3/4] drm/xe/xe_guc_submit: Allow lr exec queues to be banned Jonathan Cavitt
2024-04-15 19:24   ` Summers, Stuart
2024-04-15 18:46 ` [PATCH v5 4/4] drm/xe/xe_guc_submit: Declare reset if banned or killed Jonathan Cavitt
2024-04-15 19:31 ` [PATCH v5 1/4] drm/xe/lrc: Add xe lrc ring tail function definitions Summers, Stuart
2024-04-15 19:44   ` Matthew Brost
2024-04-15 20:26     ` Cavitt, Jonathan
2024-04-15 20:29       ` Matthew Brost
2024-04-15 20:41         ` Cavitt, Jonathan
2024-04-15 22:23           ` Summers, Stuart [this message]
2024-04-15 23:16 ` ✓ CI.Patch_applied: success for series starting with [v5,1/4] " Patchwork
2024-04-15 23:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-15 23:17 ` ✓ CI.KUnit: success " Patchwork
2024-04-15 23:29 ` ✓ CI.Build: " Patchwork
2024-04-15 23:31 ` ✓ CI.Hooks: " Patchwork
2024-04-15 23:33 ` ✓ CI.checksparse: " Patchwork
2024-04-15 23:59 ` ✓ CI.BAT: " Patchwork
2024-04-16 15:54 ` ✗ CI.FULL: failure " Patchwork

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=ac576c169912f5f6663a38b1c273e7ef84122ae6.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=brian.welty@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=jonathan.cavitt@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=niranjana.vishwanathapura@intel.com \
    --cc=saurabhg.gupta@intel.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