From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v5 0/4] Keep device awake TLB invalidations and G2H in flight
Date: Fri, 19 Jul 2024 09:50:08 -0700 [thread overview]
Message-ID: <20240719165012.1512428-1-matthew.brost@intel.com> (raw)
Combine [1], [2] to fix PM issues
[1] https://patchwork.freedesktop.org/series/136226/
[2] https://patchwork.freedesktop.org/series/136219/
Matthew Brost (4):
drm/xe: Add xe_gt_tlb_invalidation_fence_init helper
drm/xe: Drop xe_gt_tlb_invalidation_wait
drm/xe: Hold a PM ref when GT TLB invalidations are inflight
drm/xe: Build PM into GuC CT layer
drivers/gpu/drm/xe/xe_device.c | 4 +
drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 201 ++++++++++--------
drivers/gpu/drm/xe/xe_gt_tlb_invalidation.h | 12 +-
.../gpu/drm/xe/xe_gt_tlb_invalidation_types.h | 4 +
drivers/gpu/drm/xe/xe_guc_ct.c | 10 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 4 +
drivers/gpu/drm/xe/xe_pt.c | 26 +--
drivers/gpu/drm/xe/xe_vm.c | 32 +--
8 files changed, 160 insertions(+), 133 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-19 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 16:50 Matthew Brost [this message]
2024-07-19 16:50 ` [PATCH v5 1/4] drm/xe: Add xe_gt_tlb_invalidation_fence_init helper Matthew Brost
2024-07-19 16:50 ` [PATCH v5 2/4] drm/xe: Drop xe_gt_tlb_invalidation_wait Matthew Brost
2024-07-19 16:50 ` [PATCH v5 3/4] drm/xe: Hold a PM ref when GT TLB invalidations are inflight Matthew Brost
2024-07-19 16:50 ` [PATCH v5 4/4] drm/xe: Build PM into GuC CT layer Matthew Brost
2024-07-19 16:54 ` ✓ CI.Patch_applied: success for Keep device awake TLB invalidations and G2H in flight (rev2) Patchwork
2024-07-19 16:55 ` ✓ CI.checkpatch: " Patchwork
2024-07-19 16:55 ` ✗ CI.KUnit: 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=20240719165012.1512428-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