Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Riana Tauro <riana.tauro@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>,
	Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH v3 0/3] drm/xe: Add configfs to load with fewer engines
Date: Fri, 23 May 2025 10:42:30 -0700	[thread overview]
Message-ID: <20250523-engine-mask-v3-0-11817dc6eb63@intel.com> (raw)

Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
Changes in v3:
- Add patch with coding style changes to header
- Split patches: the use of the mask hw_engine initialization is one and the
  configfs handling is another
- Move the lookup table outside of the function looking up the mask:
  this will also be used in other patches in future
- Change the _show() method to pretty-print engine names: it's not the
  same format as passed in, but covers the "what was exactly parsed"
  while at the same time not require one to lookup the indexes in the
  source code (Stuart)
- Avoid the term "fuse off" (Matt Roper)
- Handle gcscs (Matt Roper)
- Improve and fold conditions for checking if the engine instance is out
  of bounds (Matt Roper)
- Link to v2: https://lore.kernel.org/r/20250520-engine-mask-v2-1-46e76f935b35@intel.com

Changes in v2:
- Fix build with CONFIG_CONFIGFS_FS=n
- Link to v1: https://lore.kernel.org/r/20250520-engine-mask-v1-1-ce6daf16d23b@intel.com
---
Lucas De Marchi (3):
      drm/xe/configfs: Drop trailing semicolons
      drm/xe: Allow to disable engines
      drm/xe/configfs: Add attribute to disable engines

 drivers/gpu/drm/xe/xe_configfs.c  | 148 ++++++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_configfs.h  |  10 +--
 drivers/gpu/drm/xe/xe_hw_engine.c |  20 ++++++
 3 files changed, 174 insertions(+), 4 deletions(-)

base-commit: 1bb9b646d6ead84cf3f16c724f7bca2cad161839
change-id: 20250520-engine-mask-f6f5962afa42

Lucas De Marchi


             reply	other threads:[~2025-05-23 17:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-23 17:42 Lucas De Marchi [this message]
2025-05-23 17:42 ` [PATCH v3 1/3] drm/xe/configfs: Drop trailing semicolons Lucas De Marchi
2025-05-23 20:52   ` Matt Roper
2025-05-23 17:42 ` [PATCH v3 2/3] drm/xe: Allow to disable engines Lucas De Marchi
2025-05-23 21:02   ` Matt Roper
2025-05-27 19:20     ` Lucas De Marchi
2025-05-23 17:42 ` [PATCH v3 3/3] drm/xe/configfs: Add attribute " Lucas De Marchi
2025-05-23 21:21   ` Matt Roper
2025-05-27 14:35     ` Lucas De Marchi
2025-05-26  9:45   ` Jani Nikula
2025-05-27 14:11     ` Lucas De Marchi
2025-05-23 17:48 ` ✓ CI.Patch_applied: success for drm/xe: Add configfs to load with fewer engines (rev3) Patchwork
2025-05-23 17:48 ` ✓ CI.checkpatch: " Patchwork
2025-05-23 17:50 ` ✓ CI.KUnit: " Patchwork
2025-05-23 18:00 ` ✓ CI.Build: " Patchwork
2025-05-23 18:02 ` ✓ CI.Hooks: " Patchwork
2025-05-23 18:04 ` ✓ CI.checksparse: " Patchwork
2025-05-23 18:26 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-24 11:12 ` ✗ Xe.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=20250523-engine-mask-v3-0-11817dc6eb63@intel.com \
    --to=lucas.demarchi@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=stuart.summers@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