All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Hold rpm wakeref for printing the engine's register state
Date: Mon, 12 Feb 2018 13:34:53 +0000	[thread overview]
Message-ID: <151844249342.18923.6009366094660667843@mail.alporthouse.com> (raw)
In-Reply-To: <87eflquyjt.fsf@gaia.fi.intel.com>

Quoting Mika Kuoppala (2018-02-12 13:28:54)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> 
> > When dumping the engine, we print out the current register values. This
> > requires the rpm wakeref. If the device is alseep, we can assume the
> > engine is asleep (and the register state is uninteresting) so skip and
> > only acquire the rpm wakeref if the device is already awake.
> >
> > Reported-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> > ---
> > +     if (intel_runtime_pm_get_if_in_use(engine->i915)) {
> > +             intel_engine_print_registers(engine, m);
> > +             intel_runtime_pm_put(engine->i915);
> > +     } else {
> > +             drm_printf(m, "Device is alseep; skipping register dump\n");
> > +     }
> 
> s/alseep/asleep
> 
> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>

Done, and both pushed. Now to try Tvrtko's warning patch on the new
baseline. Thanks,
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-02-12 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 10:24 [PATCH] drm/i915: Hold rpm wakeref for printing the engine's register state Chris Wilson
2018-02-12 10:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-12 12:45 ` ✓ Fi.CI.IGT: " Patchwork
2018-02-12 13:28 ` [PATCH] " Mika Kuoppala
2018-02-12 13:34   ` Chris Wilson [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=151844249342.18923.6009366094660667843@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.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.