From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: nirmoy.das@intel.com, rodrigo.vivi@intel.com
Subject: [PATCH 0/1] Build PM into GuC CT layer
Date: Thu, 18 Jul 2024 01:45:18 -0700 [thread overview]
Message-ID: <20240718084519.1478010-1-matthew.brost@intel.com> (raw)
Alternative solution to [1] to fix GT TLB invalidation issue raised in
[2].
Matt
[1] https://patchwork.freedesktop.org/series/136219/
[2] https://patchwork.freedesktop.org/series/136145/
Matthew Brost (1):
drm/xe: Build PM into GuC CT layer
drivers/gpu/drm/xe/xe_guc_ct.c | 5 +++++
drivers/gpu/drm/xe/xe_guc_submit.c | 4 ++++
2 files changed, 9 insertions(+)
--
2.34.1
next reply other threads:[~2024-07-18 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 8:45 Matthew Brost [this message]
2024-07-18 8:45 ` [PATCH 1/1] drm/xe: Build PM into GuC CT layer Matthew Brost
2024-07-18 8:49 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-18 8:50 ` ✓ CI.checkpatch: " Patchwork
2024-07-18 8:51 ` ✓ CI.KUnit: " Patchwork
2024-07-18 9:04 ` ✓ CI.Build: " Patchwork
2024-07-18 9:08 ` ✓ CI.Hooks: " Patchwork
2024-07-18 9:10 ` ✓ CI.checksparse: " Patchwork
2024-07-18 9:35 ` ✗ CI.BAT: 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=20240718084519.1478010-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@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