From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Move parking-while-active warning to intel_engines_park()
Date: Fri, 27 Oct 2017 16:12:23 +0300 [thread overview]
Message-ID: <87fua4g2fc.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20171027110617.31745-3-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> We will want to break this down to give detailed per-engine warnings as
> to why we still think we are active as we attempt to park the engines.
> For the first step, just move the warning verbatim from the idle-worker
> to intel_engines_park().
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-27 13:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 11:06 [PATCH 1/4] drm: Enable pr_debug() for drm_printer Chris Wilson
2017-10-27 11:06 ` [PATCH 2/4] drm/i915: Enable pr_debug() for CI debugging Chris Wilson
2017-10-27 11:06 ` [PATCH 3/4] drm/i915: Move parking-while-active warning to intel_engines_park() Chris Wilson
2017-10-27 13:12 ` Mika Kuoppala [this message]
2017-10-27 11:06 ` [PATCH 4/4] drm/i915: Give more details for the active-when-parking warning for the engines Chris Wilson
2017-10-27 13:25 ` Mika Kuoppala
2017-10-27 13:33 ` Chris Wilson
2017-11-01 15:12 ` Chris Wilson
2017-10-27 12:44 ` ✓ Fi.CI.BAT: success for series starting with [1/4] drm: Enable pr_debug() for drm_printer Patchwork
2017-10-27 15:47 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-01 17:20 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-11-01 17:45 ` ✓ Fi.CI.BAT: success " 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=87fua4g2fc.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.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 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.