From: Andi Shyti <andi.shyti@linux.intel.com>
To: Chris Wilson <chris.p.wilson@linux.intel.com>,
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/4] Invalidate TLB cache for all GT's
Date: Tue, 1 Aug 2023 16:19:51 +0200 [thread overview]
Message-ID: <20230801141955.383305-1-andi.shyti@linux.intel.com> (raw)
Hi,
This series revisits a once-trendy topic: TLB invalidation
support for multi-gt. It's a theme that's been passed around and
reshaped by several of us.
I've filtered out most of the original changes from this series,
initially sent by Mauro [1]. His ideas were inspired by some
changes from Chris, who in turn was inspired by a change from
me[2], all of which stemmed from offline talks by Chris (it's
like a game of inspiration tag!).
What I've done is simply rebase and refactor the patches,
focusing solely on the changes needed for multi-gt TLB
invalidation in MMIO memory. The result is a leaner, more
targeted proposal.
Other patches from the original series might follow.
Thanks,
Andi
[1] https://patchwork.freedesktop.org/series/106293/
[2] https://patchwork.freedesktop.org/series/103831/
Andi Shyti (2):
i915/drm/gt: Move the gt defines in the gt directory
drm/i915: Remove unnecessary include
Chris Wilson (2):
drm/i915/gt: Move TLB invalidation to its own file
drm/i915: Invalidate the TLBs on each GT
drivers/gpu/drm/i915/Makefile | 1 +
.../gpu/drm/i915/gem/i915_gem_object_types.h | 4 +-
drivers/gpu/drm/i915/gem/i915_gem_pages.c | 15 +-
drivers/gpu/drm/i915/gt/intel_gt.c | 140 +--------------
drivers/gpu/drm/i915/gt/intel_gt.h | 12 --
drivers/gpu/drm/i915/gt/intel_gt_defines.h | 11 ++
drivers/gpu/drm/i915/gt/intel_ppgtt.c | 4 +-
drivers/gpu/drm/i915/gt/intel_tlb.c | 159 ++++++++++++++++++
drivers/gpu/drm/i915/gt/intel_tlb.h | 29 ++++
drivers/gpu/drm/i915/gt/selftest_tlb.c | 3 +-
drivers/gpu/drm/i915/i915_drv.h | 1 -
drivers/gpu/drm/i915/i915_vma.c | 15 +-
12 files changed, 231 insertions(+), 163 deletions(-)
create mode 100644 drivers/gpu/drm/i915/gt/intel_gt_defines.h
create mode 100644 drivers/gpu/drm/i915/gt/intel_tlb.c
create mode 100644 drivers/gpu/drm/i915/gt/intel_tlb.h
--
2.40.1
next reply other threads:[~2023-08-01 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:19 Andi Shyti [this message]
2023-08-01 14:19 ` [Intel-gfx] [PATCH 1/4] drm/i915/gt: Move TLB invalidation to its own file Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 2/4] i915/drm/gt: Move the gt defines in the gt directory Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 3/4] drm/i915: Invalidate the TLBs on each GT Andi Shyti
2023-08-01 14:19 ` [Intel-gfx] [PATCH 4/4] drm/i915: Remove unnecessary include Andi Shyti
2023-08-01 14:40 ` [Intel-gfx] [PATCH 0/4] Invalidate TLB cache for all GT's Mauro Carvalho Chehab
2023-08-01 16:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-08-01 16:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-01 17:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-01 21:57 ` [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=20230801141955.383305-1-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mauro.chehab@linux.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