All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Arshad Mehmood <arshad.mehmood@intel.com>,
	Chris Wilson <chris.p.wilson@linux.intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>,
	Andi Shyti <andi.shyti@kernel.org>
Subject: [PATCH v2 0/6] Remove I915_ENGINE_FIRST_RENDER_COMPUTE
Date: Thu, 27 Mar 2025 00:39:59 +0100	[thread overview]
Message-ID: <20250326234005.1574688-1-andi.shyti@linux.intel.com> (raw)

Hi,

While testing the multi-CCS static load balancing, Arshad  
discovered that the CCS workaround was being applied twice, due  
to commit [*].

Further discussions with Lucas led to rethinking the purpose of  
I915_ENGINE_FIRST_RENDER_COMPUTE. This flag was originally  
introduced to handle platforms with different CCS/RCS setups.  
However, for all GPUs currently supported by i915, we can assume  
the presence of at least one RCS engine, so the logic can shift  
to focus on the first CCS engine.

Based on this, the six patches in this series are mostly  
cleanup, with two main goals:

 1. Ensure the CCS engine workaround is applied only once  
 2. Remove the I915_ENGINE_FIRST_RENDER_COMPUTE flag

Thanks,  
Andi

[*] 1bfc03b13752 ("drm/i915: Remove special handling for !RCS_MASK()")

Changelog:
==========
v1 -> v2
 - During workaround set-up, avoid checking for
   FIRST_RENDER_COMPUTE, but move the logic to the CCS engine
   section.
 - Define the FIRST_CCS flag which checks for the CCS engine
   with the lowest istance number.
 - Remove the I915_ENGINE_FIRST_RENDER_COMPUTE flag and use
   FIRST_CCS() instead for everyone using it.

Andi Shyti (6):
  drm/i915: Add the FIRST_CCS() helper
  drm/i915/gt: Move CCS workaround to the correct section
  drm/i915/gt: Remove FIRST_RENDER_COMPUTE in workaround
  drm/i915/gt: Check for the first CCS instead of FIRST_RENDER_COMPUTE
  drm/i915/gt/uc: Use FIRST_CCS() helper for one-time CCS operations
  drm/i915/gt: Remove unused I915_ENGINE_FIRST_RENDER_COMPUTE flag

 drivers/gpu/drm/i915/gt/intel_engine_cs.c     |  4 --
 drivers/gpu/drm/i915/gt/intel_engine_types.h  |  3 +-
 .../drm/i915/gt/intel_execlists_submission.c  |  2 +-
 drivers/gpu/drm/i915/gt/intel_workarounds.c   | 72 +++++++++----------
 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c    |  3 +-
 .../gpu/drm/i915/gt/uc/intel_guc_submission.c |  2 +-
 drivers/gpu/drm/i915/i915_drv.h               |  3 +
 7 files changed, 41 insertions(+), 48 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-03-26 23:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 23:39 Andi Shyti [this message]
2025-03-26 23:40 ` [PATCH v2 1/6] drm/i915: Add the FIRST_CCS() helper Andi Shyti
2025-03-27 10:42   ` Jani Nikula
2025-03-27 11:05     ` Andi Shyti
2025-03-26 23:40 ` [PATCH v2 2/6] drm/i915/gt: Move CCS workaround to the correct section Andi Shyti
2025-04-23 14:06   ` Lucas De Marchi
2025-03-26 23:40 ` [PATCH v2 3/6] drm/i915/gt: Remove FIRST_RENDER_COMPUTE in workaround Andi Shyti
2025-03-26 23:40 ` [PATCH v2 4/6] drm/i915/gt: Check for the first CCS instead of FIRST_RENDER_COMPUTE Andi Shyti
2025-03-26 23:40 ` [PATCH v2 5/6] drm/i915/gt/uc: Use FIRST_CCS() helper for one-time CCS operations Andi Shyti
2025-03-26 23:40 ` [PATCH v2 6/6] drm/i915/gt: Remove unused I915_ENGINE_FIRST_RENDER_COMPUTE flag Andi Shyti
2025-04-23 13:57   ` Lucas De Marchi
2025-03-27  0:13 ` ✗ Fi.CI.CHECKPATCH: warning for Remove I915_ENGINE_FIRST_RENDER_COMPUTE Patchwork
2025-03-27  0:14 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-27  3:13 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-27  4:52 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-23 13:54 ` [PATCH v2 0/6] " Lucas De Marchi

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=20250326234005.1574688-1-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=arshad.mehmood@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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 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.