From: Andi Shyti <andi.shyti@linux.intel.com>
To: Nirmoy Das <nirmoy.das@linux.intel.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
linux-stable <stable@vger.kernel.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-evel <dri-devel@lists.freedesktop.org>,
Matt Roper <matthew.d.roper@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v8 6/9] drm/i915/gt: Refactor intel_emit_pipe_control_cs() in a single function
Date: Mon, 24 Jul 2023 11:16:53 +0200 [thread overview]
Message-ID: <ZL5BhY6C2uzqd/bU@ashyti-mobl2.lan> (raw)
In-Reply-To: <dc09292f-e2e8-c800-b39e-99f5364a8a76@linux.intel.com>
Hi Nirmoy,
> static int mtl_dummy_pipe_control(struct i915_request *rq)
> {
> /* Wa_14016712196 */
> if (IS_MTL_GRAPHICS_STEP(rq->engine->i915, M, STEP_A0, STEP_B0) ||
> - IS_MTL_GRAPHICS_STEP(rq->engine->i915, P, STEP_A0, STEP_B0)) {
> - u32 *cs;
> -
> - /* dummy PIPE_CONTROL + depth flush */
> - cs = intel_ring_begin(rq, 6);
> - if (IS_ERR(cs))
> - return PTR_ERR(cs);
> - cs = gen12_emit_pipe_control(cs,
> - 0,
> - PIPE_CONTROL_DEPTH_CACHE_FLUSH,
> - LRC_PPHWSP_SCRATCH_ADDR);
> - intel_ring_advance(rq, cs);
> - }
> + IS_MTL_GRAPHICS_STEP(rq->engine->i915, P, STEP_A0, STEP_B0))
> + return gen12_emit_pipe_control_cs(rq, 0,
> + PIPE_CONTROL_DEPTH_CACHE_FLUSH,
> + LRC_PPHWSP_SCRATCH_ADDR);
>
> Don't think this will get backported to 5.8+. I think mtl introduced after
> that.
>
> If that is not an issue for rest of the series and then
to be honest I don't think I fully understood the stable
policies, as in this series only two are the patches that are
really fixing things and the rest are only support.
In this case I think this will produce a conflict that will be
eventually fixed (... I guess!).
> Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Thanks,
Andi
next prev parent reply other threads:[~2023-07-24 9:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 16:15 [Intel-gfx] [PATCH v8 0/9] Update AUX invalidation sequence Andi Shyti
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 1/9] drm/i915/gt: Cleanup aux invalidation registers Andi Shyti
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 2/9] drm/i915: Add the gen12_needs_ccs_aux_inv helper Andi Shyti
2023-07-21 19:12 ` Matt Roper
2023-07-24 7:52 ` Andrzej Hajda
2023-07-24 8:38 ` Nirmoy Das
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 3/9] drm/i915/gt: Ensure memory quiesced before invalidation Andi Shyti
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 4/9] drm/i915/gt: Rename flags with bit_group_X according to the datasheet Andi Shyti
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 5/9] drm/i915/gt: Enable the CCS_FLUSH bit in the pipe control Andi Shyti
2023-07-21 19:16 ` Matt Roper
2023-07-24 7:53 ` Andrzej Hajda
2023-07-24 8:47 ` Nirmoy Das
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 6/9] drm/i915/gt: Refactor intel_emit_pipe_control_cs() in a single function Andi Shyti
2023-07-24 7:54 ` Andrzej Hajda
2023-07-24 9:07 ` Nirmoy Das
2023-07-24 9:16 ` Andi Shyti [this message]
2023-07-24 9:37 ` Nirmoy Das
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 7/9] drm/i915/gt: Ensure memory quiesced before invalidation for all engines Andi Shyti
2023-07-24 8:19 ` Andrzej Hajda
2023-07-24 9:14 ` Andi Shyti
2023-07-24 9:17 ` Andrzej Hajda
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 8/9] drm/i915/gt: Poll aux invalidation register bit on invalidation Andi Shyti
2023-07-21 16:15 ` [Intel-gfx] [PATCH v8 9/9] drm/i915/gt: Support aux invalidation on all engines Andi Shyti
2023-07-24 9:42 ` Andrzej Hajda
2023-07-24 14:35 ` Andi Shyti
2023-07-21 18:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update AUX invalidation sequence (rev9) Patchwork
2023-07-21 18:04 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-07-21 18:21 ` [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=ZL5BhY6C2uzqd/bU@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nirmoy.das@intel.com \
--cc=nirmoy.das@linux.intel.com \
--cc=stable@vger.kernel.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