From: "Tapani Pälli" <tapani.palli@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org,
Tejas Upadhyay <tejas.upadhyay@intel.com>,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
Subject: Re: [PATCH] drm/i915: Fix aux invalidation with proper pipe_control flag
Date: Tue, 19 Sep 2023 15:19:23 +0300 [thread overview]
Message-ID: <aa102a2e-0b73-9f1b-8fcf-75eb5b741d03@intel.com> (raw)
In-Reply-To: <ZQmP+IWIcu1yUkSC@ashyti-mobl2.lan>
On 19.9.2023 15.11, Andi Shyti wrote:
> Hi Nirmoy,
>
> On Tue, Sep 19, 2023 at 01:47:16PM +0200, Nirmoy Das wrote:
>> The suggestion from the spec is to do l3 fabric flush not L3 flush.
>>
>> Fixes: 78a6ccd65fa3 ("drm/i915/gt: Ensure memory quiesced before
>> invalidation")
> please put this in one line.
>
>> Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
>> Cc: Andi Shyti <andi.shyti@linux.intel.com>
>> Cc: <stable@vger.kernel.org> # v5.8+
>> Cc: Nirmoy Das <nirmoy.das@intel.com>
>> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
>> Cc: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>
> and I believe
>
> Tested-by: Tapani Pälli <tapani.palli@intel.com>
Yes, tested on TGL LP (0x9a49)!
> Thanks,
> Andi
next prev parent reply other threads:[~2023-09-19 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 11:47 [PATCH] drm/i915: Fix aux invalidation with proper pipe_control flag Nirmoy Das
2023-09-19 12:11 ` Andi Shyti
2023-09-19 12:19 ` Tapani Pälli [this message]
2023-09-20 11:18 ` Nirmoy Das
2023-09-19 12:42 ` Andrzej Hajda
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=aa102a2e-0b73-9f1b-8fcf-75eb5b741d03@intel.com \
--to=tapani.palli@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=nirmoy.das@intel.com \
--cc=prathap.kumar.valsan@intel.com \
--cc=stable@vger.kernel.org \
--cc=tejas.upadhyay@intel.com \
--cc=tvrtko.ursulin@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