public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: janusz.krzysztofik@intel.com, andi.shyti@intel.com,
	matthew.d.roper@intel.com, jonathan.cavitt@intel.com,
	saurabhg.gupta@intel.com, chris.p.wilson@linux.intel.com,
	nirmoy.das@intel.com
Subject: [Intel-gfx] [PATCH v16 7/7] drm/i915: Enable GuC TLB invalidations for MTL
Date: Mon, 16 Oct 2023 07:51:09 -0700	[thread overview]
Message-ID: <20231016145109.2843611-8-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20231016145109.2843611-1-jonathan.cavitt@intel.com>

Enable GuC TLB invalidations for MTL.  Though more platforms than just
MTL support GuC TLB invalidations, MTL is presently the only platform
that requires it for any purpose, so only enable it there for now to
minimize cross-platform impact.

Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Acked-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
---
 drivers/gpu/drm/i915/i915_pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
index df7c261410f79..d4b51ececbb12 100644
--- a/drivers/gpu/drm/i915/i915_pci.c
+++ b/drivers/gpu/drm/i915/i915_pci.c
@@ -829,6 +829,7 @@ static const struct intel_device_info mtl_info = {
 	.has_flat_ccs = 0,
 	.has_gmd_id = 1,
 	.has_guc_deprivilege = 1,
+	.has_guc_tlb_invalidation = 1,
 	.has_llc = 0,
 	.has_mslice_steering = 0,
 	.has_snoop = 1,
-- 
2.25.1


  parent reply	other threads:[~2023-10-16 15:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 14:51 [Intel-gfx] [PATCH v16 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 1/7] drm/i915: Add GuC TLB Invalidation device info flags Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 2/7] drm/i915/guc: Add CT size delay helper Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 3/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 4/7] drm/i915: No TLB invalidation on suspended GT Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 5/7] drm/i915: No TLB invalidation on wedged GT Jonathan Cavitt
2023-10-16 14:51 ` [Intel-gfx] [PATCH v16 6/7] drm/i915/gt: Increase sleep in gt_tlb selftest sanitycheck Jonathan Cavitt
2023-10-16 14:51 ` Jonathan Cavitt [this message]
2023-10-16 15:14 ` [Intel-gfx] [PATCH v16 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines Cavitt, Jonathan
2023-10-17  0:30 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2) Patchwork
2023-10-17  0:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17  0:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-17  1:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-17  3:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3) Patchwork
2023-10-17  3:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17  4:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-17  5:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-17  8:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev4) Patchwork
2023-10-17  8:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17  8:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 10:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev5) Patchwork
2023-10-17 10:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 10:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 11:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev6) Patchwork
2023-10-17 11:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 11:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 12:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev7) Patchwork
2023-10-17 12:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 12:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-17 15:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev8) Patchwork
2023-10-17 15:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-17 15:31 ` [Intel-gfx] ✗ Fi.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=20231016145109.2843611-8-jonathan.cavitt@intel.com \
    --to=jonathan.cavitt@intel.com \
    --cc=andi.shyti@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=janusz.krzysztofik@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=nirmoy.das@intel.com \
    --cc=saurabhg.gupta@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