From: Jesus Narvaez <jesus.narvaez@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Tangudu Tilak Tirumalesh <tilak.tirumalesh.tangudu@intel.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Alan Previn <alan.previn.teres.alexis@intel.com>,
Jesus Narvaez <jesus.narvaez@intel.com>
Subject: [PATCH v5 0/2] drm/xe: Handle GuC semaphore instruction field check error
Date: Fri, 20 Nov 2026 21:11:12 +0200 [thread overview]
Message-ID: <20261120191111.4097737-4-jesus.narvaez@intel.com> (raw)
This series enables the driver to opt in to have the GuC check the SW Token Info
field of 64 bit semaphore instructions and then handle the G2H received from the
GuC when an unsupported value is detected.
Originally, I only had the patch to opt in to the GuC feature, but after
becoming aware of the series to add and use the has_sem64 flag, I added the
has_sem64 flag definition to this series and updated the opt-in patch to use the
new flag, with Tilak's permission.
Patches:
1. drm/xe: Add has_sem64 bit to graphics/media IP descriptors
Tilak's patch, carried over to this series unmodified (his v2)
2. drm/xe/guc: Handle GuC semaphore instruction field check error
Opts in to the GuC check when has_sem64 is set, and handles the G2H
Changes in v5:
- Patch 1: Updated to Tilak's v2, which now only compares has_sem64 when both
GTs are present (Daniele). Added Daniele's Reviewed-by.
- Patch 2: No changes from v4.
Changes in v4:
- Patch 1: Added Tilak's patch to series, carried over unmodified.
- Patch 2: Updated to use the has_sem64 flag in the opt-in condition and updated
comments accordingly. Daniele's Reviewed-by for v3 is kept with his
permission.
v3 of the GuC patch: https://lore.kernel.org/all/20261029202643.2233648-2-jesus.narvaez@intel.com/
Tilak's patch: https://lore.kernel.org/all/20261120120231.748267-2-tilak.tirumalesh.tangudu@intel.com/
Jesus Narvaez (1):
drm/xe/guc: Handle GuC semaphore instruction field check error
Tangudu Tilak Tirumalesh (1):
drm/xe: Add has_sem64 bit to graphics/media IP descriptors
drivers/gpu/drm/xe/abi/guc_actions_abi.h | 1 +
drivers/gpu/drm/xe/abi/guc_klvs_abi.h | 10 ++++++
drivers/gpu/drm/xe/xe_gt_types.h | 2 ++
drivers/gpu/drm/xe/xe_guc.c | 10 ++++++
drivers/gpu/drm/xe/xe_guc_ct.c | 4 +++
drivers/gpu/drm/xe/xe_guc_submit.c | 46 ++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_guc_submit.h | 2 ++
drivers/gpu/drm/xe/xe_pci.c | 27 ++++++++++++--
drivers/gpu/drm/xe/xe_pci_types.h | 2 ++
drivers/gpu/drm/xe/xe_trace.h | 5 +++
10 files changed, 107 insertions(+), 2 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-20 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 19:11 Jesus Narvaez [this message]
2026-11-20 19:11 ` [PATCH v5 1/2] drm/xe: Add has_sem64 bit to graphics/media IP descriptors Jesus Narvaez
2026-11-20 19:45 ` sashiko-bot
2026-11-20 19:11 ` [PATCH v5 2/2] drm/xe/guc: Handle GuC semaphore instruction field check error Jesus Narvaez
2026-11-20 19:23 ` ✗ CI.checkpatch: warning for drm/xe: Handle GuC semaphore instruction field check error (rev2) Patchwork
2026-11-20 19:25 ` ✓ CI.KUnit: success " Patchwork
2026-11-20 20:08 ` ✓ Xe.CI.BAT: " 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=20261120191111.4097737-4-jesus.narvaez@intel.com \
--to=jesus.narvaez@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tilak.tirumalesh.tangudu@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