public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry
Date: Fri, 21 Feb 2020 10:28:16 +0200	[thread overview]
Message-ID: <37e6fded-72f3-6480-6ed8-6591c2d2733b@linux.intel.com> (raw)
In-Reply-To: <158227331733.3099.1298656919493160116@skylake-alporthouse-com>

On 2020-02-21 10:21, Chris Wilson wrote:
> Quoting Martin Peres (2020-02-21 07:33:59)
>> On 2020-02-20 19:41, Chris Wilson wrote:
>>> Since we check before and then after each debugfs entry, we do not need
>>> to check before each time as well. We will error out as soon as it does
>>> fail, at all other times we know the system to be idle.
>>>
>>> No impact on runtime for glk (which apparently is one of the better
>>> behaving systems).
>>>
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Martin Peres <martin.peres@linux.intel.com>
>>
>> I don't like this patch because the first read might not have the gpu
>> suspended, and there shouldn't be much overhead in checking twice rather
>> than once.
>>
>> What's your rationale here?
> 
> We always do a check before after each file. We start in a known state,
> and expect to be able to return to that suspended state, and the _real_
> guts of the test is that any device access is accounted for.
> 
> assert(suspended) would be a better check for non-interference.

I would feel better with assert(suspended) added, but would it really
speed anything up since I assume wait_for_suspended() should be
instantaneous if we are already suspended, right?

>  
>> To me, the issue is that some platforms suspend in milliseconds while
>> some take seconds, and that might be indicative a real bug in the driver.
> 
> Exactly.

Good to hear :)

> -Chris
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-02-21  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 17:41 [igt-dev] [PATCH i-g-t] i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry Chris Wilson
2020-02-20 19:56 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-21  7:33 ` [igt-dev] [PATCH i-g-t] " Martin Peres
2020-02-21  8:21   ` Chris Wilson
2020-02-21  8:28     ` Martin Peres [this message]
2020-02-21 13:55       ` Chris Wilson
2020-02-21 13:56 ` [Intel-gfx] " Chris Wilson
2020-02-24  9:16   ` [igt-dev] " Martin Peres
2020-02-24  9:59     ` Chris Wilson
2020-02-21 15:38 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry (rev2) Patchwork
2020-02-23  4:27 ` [igt-dev] ✓ Fi.CI.IGT: success for i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry Patchwork
2020-02-24 10:52 ` [igt-dev] ✓ Fi.CI.IGT: success for i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry (rev2) 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=37e6fded-72f3-6480-6ed8-6591c2d2733b@linux.intel.com \
    --to=martin.peres@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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