Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Subject: Re: [PATCH] drm/i915: Squelch nop wait-for-idle trace
Date: Tue, 23 Jul 2019 15:54:56 +0000	[thread overview]
Message-ID: <017f7d80f8a92b689d820a3c68b68196e747a04f.camel@intel.com> (raw)
In-Reply-To: <20190723091218.5886-1-chris@chris-wilson.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1509 bytes --]

On Tue, 2019-07-23 at 10:12 +0100, Chris Wilson wrote:
> If the system is already idle, omit the GEM_TRACE saying we are about
> to
> wait for idle. It looks confusing in the logs to see a continual
> stream
> of wait-for-idle, as one immediately assumes it is stuck in a loop.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

Reviewed-by: Stuart Summers <stuart.summers@intel.com>

> ---
>  drivers/gpu/drm/i915/i915_gem.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_gem.c
> b/drivers/gpu/drm/i915/i915_gem.c
> index c6ba350e6e4f..01dd0d1d9bf6 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -951,15 +951,15 @@ wait_for_timelines(struct drm_i915_private
> *i915,
>  int i915_gem_wait_for_idle(struct drm_i915_private *i915,
>  			   unsigned int flags, long timeout)
>  {
> +	/* If the device is asleep, we have no requests outstanding */
> +	if (!READ_ONCE(i915->gt.awake))
> +		return 0;
> +
>  	GEM_TRACE("flags=%x (%s), timeout=%ld%s, awake?=%s\n",
>  		  flags, flags & I915_WAIT_LOCKED ? "locked" :
> "unlocked",
>  		  timeout, timeout == MAX_SCHEDULE_TIMEOUT ? "
> (forever)" : "",
>  		  yesno(i915->gt.awake));
>  
> -	/* If the device is asleep, we have no requests outstanding */
> -	if (!READ_ONCE(i915->gt.awake))
> -		return 0;
> -
>  	timeout = wait_for_timelines(i915, flags, timeout);
>  	if (timeout < 0)
>  		return timeout;

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2019-07-23 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23  9:12 [PATCH] drm/i915: Squelch nop wait-for-idle trace Chris Wilson
2019-07-23 10:35 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-07-23 12:26 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-23 15:54 ` Summers, Stuart [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=017f7d80f8a92b689d820a3c68b68196e747a04f.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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