From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: [Intel-xe] [PATCH 0/4] GuC submission with doorbells
Date: Tue, 28 Mar 2023 14:09:16 -0700 [thread overview]
Message-ID: <20230328210920.2110910-1-matthew.brost@intel.com> (raw)
More details:
https://gitlab.freedesktop.org/drm/xe/kernel/-/merge_requests/305
https://gitlab.freedesktop.org/drm/xe/kernel/-/merge_requests/288/
Matthew Brost (4):
drm/xe/guc: Read HXG fields from DW1 of G2H response
drm/xe/guc: Return the lower part of blocking H2G message
drm/xe/guc: Use doorbells for submission if possible
drm/xe/guc: Print doorbell ID in GuC engine debugfs entry
drivers/gpu/drm/xe/xe_guc.c | 6 +
drivers/gpu/drm/xe/xe_guc_ct.c | 12 +-
drivers/gpu/drm/xe/xe_guc_engine_types.h | 7 +
drivers/gpu/drm/xe/xe_guc_pc.c | 6 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 302 ++++++++++++++++++++++-
drivers/gpu/drm/xe/xe_guc_submit.h | 1 +
drivers/gpu/drm/xe/xe_guc_types.h | 4 +
drivers/gpu/drm/xe/xe_huc.c | 2 +-
drivers/gpu/drm/xe/xe_trace.h | 5 +
9 files changed, 333 insertions(+), 12 deletions(-)
--
2.34.1
next reply other threads:[~2023-03-28 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:09 Matthew Brost [this message]
2023-03-28 21:09 ` [Intel-xe] [PATCH 1/4] drm/xe/guc: Read HXG fields from DW1 of G2H response Matthew Brost
2023-03-30 15:38 ` Michal Wajdeczko
2023-04-21 8:21 ` Matthew Brost
2023-03-28 21:09 ` [Intel-xe] [PATCH 2/4] drm/xe/guc: Return the lower part of blocking H2G message Matthew Brost
2023-03-28 21:09 ` [Intel-xe] [PATCH 3/4] drm/xe/guc: Use doorbells for submission if possible Matthew Brost
2023-03-28 21:09 ` [Intel-xe] [PATCH 4/4] drm/xe/guc: Print doorbell ID in GuC engine debugfs entry Matthew Brost
2023-03-28 21:11 ` [Intel-xe] ✓ CI.Patch_applied: success for GuC submission with doorbells Patchwork
2023-03-28 21:12 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-03-28 21:16 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-28 21:38 ` [Intel-xe] ○ CI.BAT: info " 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=20230328210920.2110910-1-matthew.brost@intel.com \
--to=matthew.brost@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;
as well as URLs for NNTP newsgroup(s).