From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Wake device for emitting request during selftest
Date: Wed, 12 Apr 2017 11:50:27 +0300 [thread overview]
Message-ID: <1491987027.3274.15.camel@linux.intel.com> (raw)
In-Reply-To: <20170411234427.14841-3-chris@chris-wilson.co.uk>
On ke, 2017-04-12 at 00:44 +0100, Chris Wilson wrote:
> igt_mmap_offset_exhaustion() selftest was using live requests to make an
> object busy, but we did not hold a runtime pm wakeref for submitting the
> requests. Acquire it to avoid triggering "RPM wakelock ref not held
> during HW access" warnings.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-12 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 23:44 [PATCH 1/3] drm/i915: Add stub mmio read/write routines to mock device Chris Wilson
2017-04-11 23:44 ` [PATCH 2/3] drm/i915: Pretend the engine is always idle when mocking Chris Wilson
2017-04-12 8:49 ` Joonas Lahtinen
2017-04-11 23:44 ` [PATCH 3/3] drm/i915: Wake device for emitting request during selftest Chris Wilson
2017-04-12 8:50 ` Joonas Lahtinen [this message]
2017-04-12 0:01 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Add stub mmio read/write routines to mock device Patchwork
2017-04-12 8:48 ` [PATCH 1/3] " Joonas Lahtinen
2017-04-12 9:21 ` [PATCH v2] " Chris Wilson
2017-04-12 9:36 ` Michal Wajdeczko
2017-04-12 12:28 ` Joonas Lahtinen
2017-04-12 10:30 ` ✓ Fi.CI.BAT: success for series starting with [v2] drm/i915: Add stub mmio read/write routines to mock device (rev2) Patchwork
2017-04-12 12:40 ` Chris Wilson
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=1491987027.3274.15.camel@linux.intel.com \
--to=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox