Re: [igt-dev] [PATCH i-g-t v2 1/4] i915/i915_pm_rpm: Enable PC8+ residency test

["Gupta, Anshuman" <anshuman.gupta@intel.com>]

> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: Wednesday, February 3, 2021 5:08 PM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>; igt-
> dev@lists.freedesktop.org
> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> Subject: Re: [igt-dev] [PATCH i-g-t v2 1/4] i915/i915_pm_rpm: Enable PC8+
> residency test
> 
> Quoting Anshuman Gupta (2021-02-03 10:03:07)
> > Enabled pc8-residency test for each platform that supports pc8.
> > Bifurcate pc8-residency is display-on and display-off test case.
> >
> > Negative testing of PC8 residency on HASWELL/BROADWELL while display
> > being "on" is removed as it saves CI time and there is no ROI of such
> > testing.
> 
> Is checking for !pc8 in the atomic state checker? That would be a good, very
> precise, runtime debug check.
Could you please elaborate a little bit, I have not got much of this review comment.
> 
> Still a 30s timeout? Is that overly conservative? Is there some way to kick it into
> pc8 for fast tests with one or two slow let-it-enter-pc8-naturally tests?
From GFX side if it enters RC6 and display is off, 30 seconds is really conservative.
With RC6 it can reach PC2R and PC3 easily but for PC8 it also depends on other component as well.
That is why 30 second conservative time is safer to use. 

PC2R -> PC3
PC2R -> PC8
PC2R -> PC10
Transition from PC2R to deeper package C state are dependent upon entire system-wide negotiated LTR values.
 How about PC3 tests  in case we are looking for gem specific fast tests ?  
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev