From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/2] TLB invalidation cleanup
Date: Mon, 19 Dec 2022 10:13:14 +0000 [thread overview]
Message-ID: <20221219101316.168129-1-tvrtko.ursulin@linux.intel.com> (raw)
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
First patch to make the platform check not catch all due current lack of
automated testing.
Second patch to consolidate the code a bit and move invariant setup at engine
init time. Don't think I want to merge this one until some test coverage can be
had.
Tvrtko Ursulin (2):
drm/i915: Do not cover all future platforms in TLB invalidation
drm/i915: Consolidate TLB invalidation flow
drivers/gpu/drm/i915/gt/intel_engine_cs.c | 93 ++++++++++++++
drivers/gpu/drm/i915/gt/intel_engine_types.h | 15 +++
drivers/gpu/drm/i915/gt/intel_gt.c | 124 +++----------------
3 files changed, 128 insertions(+), 104 deletions(-)
--
2.34.1
next reply other threads:[~2022-12-19 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:13 Tvrtko Ursulin [this message]
2022-12-19 10:13 ` [Intel-gfx] [PATCH 1/2] drm/i915: Do not cover all future platforms in TLB invalidation Tvrtko Ursulin
2022-12-19 15:40 ` Andrzej Hajda
2022-12-19 10:13 ` [Intel-gfx] [PATCH 2/2] drm/i915: Consolidate TLB invalidation flow Tvrtko Ursulin
2022-12-19 16:10 ` Andrzej Hajda
2023-01-03 19:57 ` Matt Roper
2023-01-04 8:46 ` Andrzej Hajda
2023-01-04 10:08 ` Tvrtko Ursulin
2023-01-04 17:41 ` Matt Roper
2023-01-04 21:58 ` Andrzej Hajda
2023-01-05 13:06 ` Tvrtko Ursulin
2023-01-06 0:19 ` Matt Roper
2022-12-19 14:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for TLB invalidation cleanup Patchwork
2022-12-19 15:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-12-20 3:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20221219101316.168129-1-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@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