Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/xe: Ensure fixed_slice_mode gets set after ccs_mode change
Date: Thu, 27 Mar 2025 20:24:58 -0700	[thread overview]
Message-ID: <Z+YWigl2GVyLiUcW@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250327210205.GI1439735@mdroper-desk1.amr.corp.intel.com>

On Thu, Mar 27, 2025 at 02:02:05PM -0700, Matt Roper wrote:
> On Thu, Mar 27, 2025 at 11:56:04AM -0700, Niranjana Vishwanathapura wrote:
> > The RCU_MODE_FIXED_SLICE_CCS_MODE setting is not getting invoked
> > in the gt reset path after the ccs_mode setting by the user.
> > Add it to engine register update list (in hw_engine_setup_default_state())
> > which ensures it gets set in the gt reset and engine reset paths.
> > 
> > v2: Add register update to engine list to ensure it gets updated
> > after engine reset also.
> > 
> > Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
> 
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> 

Merged this to drm-xe-next at the request of Saurabhg. I added a fixes
tag so this gets backported.

Matt

> > ---
> >  drivers/gpu/drm/xe/xe_hw_engine.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
> > index 8c05fd30b7df..93241fd0a4ba 100644
> > --- a/drivers/gpu/drm/xe/xe_hw_engine.c
> > +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
> > @@ -389,12 +389,6 @@ xe_hw_engine_setup_default_lrc_state(struct xe_hw_engine *hwe)
> >  				 blit_cctl_val,
> >  				 XE_RTP_ACTION_FLAG(ENGINE_BASE)))
> >  		},
> > -		/* Use Fixed slice CCS mode */
> > -		{ XE_RTP_NAME("RCU_MODE_FIXED_SLICE_CCS_MODE"),
> > -		  XE_RTP_RULES(FUNC(xe_hw_engine_match_fixed_cslice_mode)),
> > -		  XE_RTP_ACTIONS(FIELD_SET(RCU_MODE, RCU_MODE_FIXED_SLICE_CCS_MODE,
> > -					   RCU_MODE_FIXED_SLICE_CCS_MODE))
> > -		},
> >  		/* Disable WMTP if HW doesn't support it */
> >  		{ XE_RTP_NAME("DISABLE_WMTP_ON_UNSUPPORTED_HW"),
> >  		  XE_RTP_RULES(FUNC(xe_rtp_cfeg_wmtp_disabled)),
> > @@ -461,6 +455,12 @@ hw_engine_setup_default_state(struct xe_hw_engine *hwe)
> >  		  XE_RTP_ACTIONS(SET(CSFE_CHICKEN1(0), CS_PRIORITY_MEM_READ,
> >  				     XE_RTP_ACTION_FLAG(ENGINE_BASE)))
> >  		},
> > +		/* Use Fixed slice CCS mode */
> > +		{ XE_RTP_NAME("RCU_MODE_FIXED_SLICE_CCS_MODE"),
> > +		  XE_RTP_RULES(FUNC(xe_hw_engine_match_fixed_cslice_mode)),
> > +		  XE_RTP_ACTIONS(FIELD_SET(RCU_MODE, RCU_MODE_FIXED_SLICE_CCS_MODE,
> > +					   RCU_MODE_FIXED_SLICE_CCS_MODE))
> > +		},
> >  	};
> >  
> >  	xe_rtp_process_to_sr(&ctx, engine_entries, ARRAY_SIZE(engine_entries), &hwe->reg_sr);
> > -- 
> > 2.43.0
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> Linux GPU Platform Enablement
> Intel Corporation

  reply	other threads:[~2025-03-28  3:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 18:56 [PATCH v2] drm/xe: Ensure fixed_slice_mode gets set after ccs_mode change Niranjana Vishwanathapura
2025-03-27 19:01 ` ✓ CI.Patch_applied: success for drm/xe: Ensure fixed_slice_mode gets set after ccs_mode change (rev2) Patchwork
2025-03-27 19:01 ` ✓ CI.checkpatch: " Patchwork
2025-03-27 19:02 ` ✓ CI.KUnit: " Patchwork
2025-03-27 19:19 ` ✓ CI.Build: " Patchwork
2025-03-27 19:21 ` ✓ CI.Hooks: " Patchwork
2025-03-27 19:23 ` ✓ CI.checksparse: " Patchwork
2025-03-27 19:45 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-27 21:02 ` [PATCH v2] drm/xe: Ensure fixed_slice_mode gets set after ccs_mode change Matt Roper
2025-03-28  3:24   ` Matthew Brost [this message]
2025-03-28  5:43 ` ✗ Xe.CI.Full: failure for drm/xe: Ensure fixed_slice_mode gets set after ccs_mode change (rev2) 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=Z+YWigl2GVyLiUcW@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=niranjana.vishwanathapura@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