From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Jonathan Cavitt <jonathan.cavitt@intel.com>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [PATCH v3] drm/i915: Flush WC GGTT only on required platforms
Date: Tue, 31 Oct 2023 11:56:25 +0100 [thread overview]
Message-ID: <59a0141f-786c-8170-c3fb-8a8d820aeac0@linux.intel.com> (raw)
In-Reply-To: <3887c6f2-687e-01d0-71c9-b2354a0df9c7@linux.intel.com>
This is now merged to gt-next
Thanks,
Nirmoy
On 10/18/2023 4:04 PM, Nirmoy Das wrote:
>
> On 10/18/2023 3:00 PM, Andi Shyti wrote:
>> Hi Nirmoy,
>>
>>>>> gen8_ggtt_invalidate() is only needed for limited set of platforms
>>>>> where GGTT is mapped as WC. This was added as way to fix WC based
>>>>> GGTT in
>>>>> commit 0f9b91c754b7 ("drm/i915: flush system agent TLBs on SNB") and
>>>>> there are no reference in HW docs that forces us to use this on
>>>>> non-WC
>>>>> backed GGTT.
>>>>>
>>>>> This can also cause unwanted side-effects on XE_HP platforms where
>>>>> GFX_FLSH_CNTL_GEN6 is not valid anymore.
>>>>>
>>>>> v2: Add a func to detect wc ggtt detection (Ville)
>>>>> v3: Improve commit log and add reference commit (Daniel)
>>>>>
>>>>> Fixes: d2eae8e98d59 ("drm/i915/dg2: Drop force_probe requirement")
>>>> I'm wondering if this is the right Fixes, though. Should this
>>>> rather be:
>>>>
>>>> Fixes: 6266992cf105 ("drm/i915/gt: remove GRAPHICS_VER == 10")
>>> Hard to find a real Fixes for this. I just want to backport this to dg2
>>> where we can have unwanted side-effects.
>> yes, this piece of code has moved around enough so to make it
>> diffuclt to track its origin.
>>
>> I think the one I found should be the correct one,
>
> That just removes a graphics ver, not related to WC GGTT map or XE_HP.
>
>> but the dg2
>> force probe removeal can also become a placeholder for DG2 fixes.
>
> Yes, I have no better ideas too.
>
>
> Regards,
>
> Nirmoy
>
>>
>> I won't complain.
>>
>> Andi
prev parent reply other threads:[~2023-10-31 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:38 [PATCH v3] drm/i915: Flush WC GGTT only on required platforms Nirmoy Das
2023-10-18 11:49 ` Andi Shyti
2023-10-18 11:58 ` Nirmoy Das
2023-10-18 13:00 ` Andi Shyti
2023-10-18 14:04 ` Nirmoy Das
2023-10-31 10:56 ` Nirmoy Das [this message]
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=59a0141f-786c-8170-c3fb-8a8d820aeac0@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--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=rodrigo.vivi@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