Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Atwood <matthew.s.atwood@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>,
	<lucas.demarchi@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: lucas.demarchi@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/2 v3] drm/xe: add gt tuning for indirect state
Date: Wed, 6 Sep 2023 14:39:47 -0700	[thread overview]
Message-ID: <ZPjxo27bJJPFezri@msatwood-mobl> (raw)
In-Reply-To: <20230824203555.GA1529860@mdroper-desk1.amr.corp.intel.com>

On Thu, Aug 24, 2023 at 01:35:55PM -0700, Matt Roper wrote:
> On Wed, Aug 23, 2023 at 12:55:33PM -0700, Matt Atwood wrote:
> > Force indirect state sampler data to only be in the dynamic state pool,
> > which is more convienent for the UMD. Behavior change mirrors similar
> > change for i915 in commit 16fc9c08f0ec ("drm/i915: disable sampler
> > indirect state in bindless heap")
> > 
> > v2: split out per engine tuning into separate patch, commit message
> > (Lucas)
> > v3: rebase
> > 
> > Bspec: 46052
> 
> These days there's no realy need to put bspec references for register
> pages on workarounds like this.  Reviewers with bspec access can already
> lookup the register directly by name and/or offset, so this isn't
> helpful like it used to be in the old days.
ack.
> 
> > 
> > Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> > ---
> >  drivers/gpu/drm/xe/regs/xe_gt_regs.h | 1 +
> >  drivers/gpu/drm/xe/xe_tuning.c       | 5 +++++
> >  2 files changed, 6 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/xe/regs/xe_gt_regs.h b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > index aa9d7fad41ee..d039e7afe466 100644
> > --- a/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > +++ b/drivers/gpu/drm/xe/regs/xe_gt_regs.h
> > @@ -298,6 +298,7 @@
> >  #define   ENABLE_SMALLPL			REG_BIT(15)
> >  #define   SC_DISABLE_POWER_OPTIMIZATION_EBB	REG_BIT(9)
> >  #define   SAMPLER_ENABLE_HEADLESS_MSG		REG_BIT(5)
> > +#define   INDIRECT_STATE_BASE_ADDR_OVERRIDE	REG_BIT(0)
> >  
> >  #define HALF_SLICE_CHICKEN7				XE_REG_MCR(0xe194, XE_REG_OPTION_MASKED)
> >  #define   DG2_DISABLE_ROUND_ENABLE_ALLOW_FOR_SSLA	REG_BIT(15)
> > diff --git a/drivers/gpu/drm/xe/xe_tuning.c b/drivers/gpu/drm/xe/xe_tuning.c
> > index 702cb41dab53..07ffda39e2e4 100644
> > --- a/drivers/gpu/drm/xe/xe_tuning.c
> > +++ b/drivers/gpu/drm/xe/xe_tuning.c
> > @@ -28,6 +28,11 @@ static const struct xe_rtp_entry_sr gt_tunings[] = {
> >  };
> >  
> >  static const struct xe_rtp_entry_sr engine_tunings[] = {
> > +	{ XE_RTP_NAME("Tuning: Set Indirect State Override"),
> > +	  XE_RTP_RULES(GRAPHICS_VERSION_RANGE(1200, XE_RTP_END_VERSION_UNDEFINED),
> 
> This matches every single platform, so this rule isn't really doing any
> good as is.
> 
> However this setting is already the hardware default on Xe2, so 1271
> would be a reasonable end version here.
ack.
> 
> > +		       FUNC(xe_rtp_match_first_render_or_compute)),
> 
> This register doesn't exist on platforms like PVC that don't have 3D
> functionality (and doesn't really make sense if there's no render).  So
> we should probably apply this rule specifically on the render engine
> rather than "first render/compute."
ack.
> 
> 
> Matt
> 
> > +	  XE_RTP_ACTIONS(SET(SAMPLER_MODE, INDIRECT_STATE_BASE_ADDR_OVERRIDE))
> > +	},
> >  	{}
> >  };
> >  
> > -- 
> > 2.40.1
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> Linux GPU Platform Enablement
> Intel Corporation

  reply	other threads:[~2023-09-06 21:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 19:55 [Intel-xe] [PATCH 1/2 v3] drm/xe: Add infrastructure for per engine tuning Matt Atwood
2023-08-23 19:55 ` [Intel-xe] [PATCH 2/2 v3] drm/xe: add gt tuning for indirect state Matt Atwood
2023-08-24 20:35   ` Matt Roper
2023-09-06 21:39     ` Matt Atwood [this message]
2023-08-23 19:58 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/2,v3] drm/xe: Add infrastructure for per engine tuning Patchwork
2023-08-23 19:58 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-23 19:59 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-23 20:03 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-23 20:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-08-23 20:04 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-23 20:31 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-08-24 20:05 ` [Intel-xe] [PATCH 1/2 v3] " Matt Roper
2023-09-06 21:40   ` Matt Atwood

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=ZPjxo27bJJPFezri@msatwood-mobl \
    --to=matthew.s.atwood@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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