All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: "Nilawar, Badal" <badal.nilawar@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"chris.p.wilson@linux.intel.com" <chris.p.wilson@linux.intel.com>,
	"Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
Subject: Re: [PATCH] drm/i915/rc6: Disable RPG during workload execution
Date: Thu, 24 Oct 2024 13:34:13 -0400	[thread overview]
Message-ID: <ZxqFFflwleAwP-ly@intel.com> (raw)
In-Reply-To: <CY5PR11MB6211F54A4FF6B214B71CC52E954E2@CY5PR11MB6211.namprd11.prod.outlook.com>

On Thu, Oct 24, 2024 at 10:28:38AM -0400, Gupta, Anshuman wrote:
> 
> 
> > -----Original Message-----
> > From: Nilawar, Badal <badal.nilawar@intel.com>
> > Sent: Wednesday, October 23, 2024 9:42 PM
> > To: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> > Cc: Andi Shyti <andi.shyti@linux.intel.com>; intel-gfx@lists.freedesktop.org;
> > Gupta, Anshuman <anshuman.gupta@intel.com>;
> > chris.p.wilson@linux.intel.com
> > Subject: Re: [PATCH] drm/i915/rc6: Disable RPG during workload execution
> > 
> > 
> > 
> > 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.
> IMO this patch should be extended for MTL and ARL as well.
> Don't disable the RPG completely, only disable it during workload submission.
> That should save power on both MTL and ARL platforms, and right thing to do.
> And patch should add the Fixes tag accordingly to the commit which disables the RPG on MTL.
> @Vivi, Rodrigo what is your opinion on above ? it seems both MTL and ADL issues are same signature.
> MTL issue got disappear as RPG is disabled globally but that will burn power.
> If window does not have this issue then it is always difficult to get proper SV support.  
> But OS like window may not catch these kind of issues as they don't reload the their graphics driver like
> Linux reload module multiple times during selftest execution. Even chrome-os does not do that.
> Not a real world use case.

So we should change the tests without impacting the real world use case.

Let's try to grab the forcewake_all when using these self-tests, except the rc6 one.

> Thanks,
> Anshuman.
> > >>
> > >> 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-24 17:34 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
2024-10-24 14:28             ` Gupta, Anshuman
2024-10-24 17:34               ` Rodrigo Vivi [this message]
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=ZxqFFflwleAwP-ly@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vinay.belgaumkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.