Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v2 0/4] Add test for G2G communications
Date: Tue,  5 Aug 2025 16:42:51 -0700	[thread overview]
Message-ID: <20250805234256.1021020-1-John.C.Harrison@Intel.com> (raw)

From: John Harrison <John.C.Harrison@Intel.com>

Platforms with multiple GuCs (multi-GT and/or multi-tile) have a
mechanism for sending messages from one GuC to another. This relies on
the KMD configuring buffers correctly and informing the GuCs about
them. Support for that was merged a while back. So add a test to go
with it.

Also, improve the firmware CSS header structure and defines to better
match the spec and to add missing fields that are useful.

v2: Tweaks for review feedback from Daniele

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>


John Harrison (4):
  drm/xe/guc: Update CSS header structures
  drm/xe/guc: Add firmware build type to available info
  drm/xe: Allow freeing of a managed bo
  drm/xe/guc: Add test for G2G communications

 drivers/gpu/drm/xe/abi/guc_actions_abi.h    |   2 +
 drivers/gpu/drm/xe/tests/xe_guc_g2g_test.c  | 776 ++++++++++++++++++++
 drivers/gpu/drm/xe/tests/xe_live_test_mod.c |   2 +
 drivers/gpu/drm/xe/xe_bo.c                  |   5 +
 drivers/gpu/drm/xe/xe_bo.h                  |   1 +
 drivers/gpu/drm/xe/xe_device_types.h        |   7 +
 drivers/gpu/drm/xe/xe_guc.c                 |   4 +
 drivers/gpu/drm/xe/xe_guc.h                 |   4 +
 drivers/gpu/drm/xe/xe_guc_ct.c              |   5 +
 drivers/gpu/drm/xe/xe_guc_fwif.h            |   1 +
 drivers/gpu/drm/xe/xe_uc_fw.c               |  25 +-
 drivers/gpu/drm/xe/xe_uc_fw_abi.h           |  64 +-
 drivers/gpu/drm/xe/xe_uc_fw_types.h         |   3 +
 13 files changed, 864 insertions(+), 35 deletions(-)
 create mode 100644 drivers/gpu/drm/xe/tests/xe_guc_g2g_test.c

-- 
2.49.0


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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 23:42 John.C.Harrison [this message]
2025-08-05 23:42 ` [PATCH v2 1/4] drm/xe/guc: Update CSS header structures John.C.Harrison
2025-09-05 21:30   ` Daniele Ceraolo Spurio
2025-08-05 23:42 ` [PATCH v2 2/4] drm/xe/guc: Add firmware build type to available info John.C.Harrison
2025-08-05 23:42 ` [PATCH v2 3/4] drm/xe: Allow freeing of a managed bo John.C.Harrison
2025-09-09 22:10   ` Daniele Ceraolo Spurio
2025-08-05 23:42 ` [PATCH v2 4/4] drm/xe/guc: Add test for G2G communications John.C.Harrison
2025-09-05 22:20   ` Daniele Ceraolo Spurio
2025-08-06  0:58 ` ✗ CI.checkpatch: warning for Add test for G2G communications (rev2) Patchwork
2025-08-06  0:59 ` ✓ CI.KUnit: success " Patchwork
2025-08-06  1:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-06  2:36 ` ✗ 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=20250805234256.1021020-1-John.C.Harrison@Intel.com \
    --to=john.c.harrison@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    /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