From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: John Harrison <John.C.Harrison@Intel.com>
Subject: [PATCH v2 0/2] drm/xe: Add support for G2G communication
Date: Tue, 19 Nov 2024 14:54:19 -0800 [thread overview]
Message-ID: <20241119225421.198838-1-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
Platforms with multiple GTs have the ability for the multiple GuCs to
talk to each other directly. This will be useful for in the future. So
start adding support for it.
v2: Couple of tweaks from review feedback - fix bo_get/put calls and
improve readability.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
John Harrison (1):
drm/xe/guc: Add support for G2G communications
Niranjana Vishwanathapura (1):
drm/xe: Allow bo mapping on multiple ggtts
drivers/gpu/drm/xe/abi/guc_actions_abi.h | 20 ++
drivers/gpu/drm/xe/display/xe_fb_pin.c | 12 +-
drivers/gpu/drm/xe/xe_bo.c | 49 ++--
drivers/gpu/drm/xe/xe_bo.h | 32 ++-
drivers/gpu/drm/xe/xe_bo_evict.c | 14 +-
drivers/gpu/drm/xe/xe_bo_types.h | 5 +-
drivers/gpu/drm/xe/xe_ggtt.c | 35 +--
drivers/gpu/drm/xe/xe_guc.c | 307 ++++++++++++++++++++++-
drivers/gpu/drm/xe/xe_guc_types.h | 10 +
9 files changed, 437 insertions(+), 47 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-19 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 22:54 John.C.Harrison [this message]
2024-11-19 22:54 ` [PATCH v2 1/2] drm/xe: Allow bo mapping on multiple ggtts John.C.Harrison
2024-11-19 22:54 ` [PATCH v2 2/2] drm/xe/guc: Add support for G2G communications John.C.Harrison
2024-11-19 22:59 ` ✗ CI.Patch_applied: failure for drm/xe: Add support for G2G communication (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-11-20 0:02 [PATCH v2 0/2] drm/xe: Add support for G2G communication John.C.Harrison
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=20241119225421.198838-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