Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
	<intel-gfx@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
	<chris.p.wilson@linux.intel.com>
Subject: Re: [PATCH] drm/i915/rc6: Disable RPG during workload execution
Date: Wed, 23 Oct 2024 21:41:56 +0530	[thread overview]
Message-ID: <1f218b09-8385-4bc2-9296-28f7ec4ed2e8@intel.com> (raw)
In-Reply-To: <3416b828-2040-4deb-8df7-e5a0e7db51b4@intel.com>



On 23-10-2024 21:31, Nilawar, Badal wrote:
> 
> 
> On 23-10-2024 20:18, Rodrigo Vivi wrote:
>> On Wed, Oct 23, 2024 at 11:03:57AM +0530, Nilawar, Badal wrote:
>>>
>>>
>>> On 22-10-2024 22:39, Rodrigo Vivi wrote:
>>>> On Tue, Oct 22, 2024 at 03:28:43PM +0200, Andi Shyti wrote:
>>>>> Hi Badal,
>>>>>
>>>>> On Tue, Oct 22, 2024 at 06:52:26PM +0530, Badal Nilawar wrote:
>>>>>> Encountering forcewake errors related to render power gating;
>>>>>
>>>>> Can you please expand your explanation here?
>>>>
>>>> yeap. More explanation please. All platforms? really?
>>>
>>> We are seeing Render forcewake timeouts on ADLP, ADLM, ADLN, TWL, 
>>> DG1, rpl.
>>
>> Is this a regression? or a new issue?
> 
> This is old issue, first reported year back.
> 
>>
>> Is this happening with Xe on these platforms? or i915 only?
> 
> i915 only. This is not reported on Xe kmd.
> 
>>
>>> Issue disappears after disabling RPG. Instead of fully disabling RPG 
>>> I am
>>> disabling it during active submissions i.e. during unpark.
>>> For MTL and ARL RPG is already disabled permanently.
>>
>> uhm. Interesting. Why that is disabled on these platforms? 
> 
>  From commit log its temporary wa to avoid fw timeouts.
> 
> perhaps we should be
>> doing the same for all GuC enabled platforms?
> 
> I think so as temporary Wa.

Correction, DG1 we are not seeing this. I think we can go with platform 
check.

Regards,
Badal


  reply	other threads:[~2024-10-23 16:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 13:22 [PATCH] drm/i915/rc6: Disable RPG during workload execution Badal Nilawar
2024-10-22 13:28 ` Andi Shyti
2024-10-22 17:09   ` Rodrigo Vivi
2024-10-23  5:33     ` Nilawar, Badal
2024-10-23 14:48       ` Rodrigo Vivi
2024-10-23 16:01         ` Nilawar, Badal
2024-10-23 16:11           ` Nilawar, Badal [this message]
2024-10-24 14:28             ` Gupta, Anshuman
2024-10-24 17:34               ` Rodrigo Vivi
2024-10-24 19:06                 ` Nilawar, Badal
2024-10-22 14:00 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-10-22 14:10 ` ✓ Fi.CI.BAT: success " Patchwork
2024-10-22 19:28 ` ✓ 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=1f218b09-8385-4bc2-9296-28f7ec4ed2e8@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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