Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH v2 2/4] drm/i915/gt: Ensure memory quiesced before invalidation
Date: Tue, 27 Jun 2023 11:43:25 +0200	[thread overview]
Message-ID: <20230627094327.134775-3-andi.shyti@linux.intel.com> (raw)
In-Reply-To: <20230627094327.134775-1-andi.shyti@linux.intel.com>

From: Jonathan Cavitt <jonathan.cavitt@intel.com>

All memory traffic must be quiesced before requesting
an aux invalidation on platforms that use Aux CCS.

Fixes: 972282c4cf24 ("drm/i915/gen12: Add aux table invalidate for all engines")
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
Cc: <stable@vger.kernel.org> # v5.8+
---
 drivers/gpu/drm/i915/gt/gen8_engine_cs.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/gen8_engine_cs.c b/drivers/gpu/drm/i915/gt/gen8_engine_cs.c
index 563efee055602..e10e1ad0e841f 100644
--- a/drivers/gpu/drm/i915/gt/gen8_engine_cs.c
+++ b/drivers/gpu/drm/i915/gt/gen8_engine_cs.c
@@ -202,6 +202,13 @@ int gen12_emit_flush_rcs(struct i915_request *rq, u32 mode)
 {
 	struct intel_engine_cs *engine = rq->engine;
 
+	/*
+	 * Aux invalidations on Aux CCS platforms require
+	 * memory traffic is quiesced prior.
+	 */
+	if (!HAS_FLAT_CCS(engine->i915))
+		mode |= EMIT_FLUSH;
+
 	if (mode & EMIT_FLUSH) {
 		u32 flags = 0;
 		int err;
-- 
2.40.1


  parent reply	other threads:[~2023-06-27  9:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  9:43 [Intel-gfx] [PATCH v2 0/4] Update AUX invalidation sequence Andi Shyti
2023-06-27  9:43 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/gt: Cleanup aux invalidation registers Andi Shyti
2023-07-12 13:51   ` Nirmoy Das
2023-06-27  9:43 ` Andi Shyti [this message]
2023-07-12 14:17   ` [Intel-gfx] [PATCH v2 2/4] drm/i915/gt: Ensure memory quiesced before invalidation Nirmoy Das
2023-07-12 15:39     ` Cavitt, Jonathan
2023-07-13  9:31       ` Nirmoy Das
2023-07-13 12:31         ` Andi Shyti
2023-07-13 14:12           ` Nirmoy Das
2023-07-13 14:23             ` Cavitt, Jonathan
2023-07-14 10:24               ` Nirmoy Das
2023-06-27  9:43 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/gt: Poll aux invalidation register bit on invalidation Andi Shyti
2023-07-12 14:24   ` Nirmoy Das
2023-06-27  9:43 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/gt: Support aux invalidation on all engines Andi Shyti
2023-07-12 14:26   ` Nirmoy Das
2023-07-12 21:58     ` Andi Shyti
2023-06-27 15:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Update AUX invalidation sequence (rev2) Patchwork
2023-06-27 16:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-28  5:16 ` [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=20230627094327.134775-3-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=mika.kuoppala@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