From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Michel Thierry <michel.thierry@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: get a runtime PM ref in i915_wedged_set
Date: Tue, 14 Mar 2017 09:37:15 -0700 [thread overview]
Message-ID: <ffe047e5-6705-baff-af73-30a40c65221f@intel.com> (raw)
In-Reply-To: <20170314002606.8838-1-michel.thierry@intel.com>
On 13/03/17 17:26, Michel Thierry wrote:
> At least in bxt (with decoupled mmio), it prevents a warning while
> capturing the reg state:
>
> [ ] WARNING: assert_rpm_wakelock_held.part.4+0x1e/0x20 [i915]
> [ ] RPM wakelock ref not held during HW access
> [ ] Call Trace:
> [ ] dump_stack+0x63/0x87
> [ ] __warn+0xd1/0xf0
> [ ] ? fwtable_write32+0x1a0/0x1a0 [i915]
> [ ] warn_slowpath_fmt+0x4f/0x60
> [ ] ? vprintk_default+0x29/0x50
> [ ] assert_rpm_wakelock_held.part.4+0x1e/0x20 [i915]
> [ ] gen9_decoupled_read32+0x18a/0x1a0 [i915]
> [ ] ? fwtable_write32+0x1a0/0x1a0 [i915]
> [ ] i915_handle_error+0x1d0/0x260 [i915]
> [ ] ? __check_object_size+0x170/0x1aa
> [ ] i915_wedged_set+0x25/0x30 [i915]
>
> These get/put were removed by commit 9c870d03674f ("drm/i915: Use RPM as the
> barrier for controlling user mmap access"), before decoupled mmio was
> added in commit 85ee17ebeedd ("drm/i915/bxt: Broxton decoupled MMIO).
>
> Reported-by: Antonio Argenziano <antonio.argenziano@intel.com>
> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
Tested-By: Antonio Argenziano <antonio.argenziano@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 9fcc4f1a86fc..89f211391ef9 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -4155,9 +4155,13 @@ i915_wedged_set(void *data, u64 val)
> if (i915_reset_in_progress(&dev_priv->gpu_error))
> return -EAGAIN;
>
> + intel_runtime_pm_get(dev_priv);
> +
> i915_handle_error(dev_priv, val,
> "Manually setting wedged to %llu", val);
>
> + intel_runtime_pm_put(dev_priv);
> +
> return 0;
> }
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-14 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 0:26 [PATCH] drm/i915: get a runtime PM ref in i915_wedged_set Michel Thierry
2017-03-14 0:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-03-14 9:09 ` [PATCH] " Chris Wilson
2017-03-14 17:05 ` Michel Thierry
2017-03-14 17:12 ` Chris Wilson
2017-03-14 16:37 ` Antonio Argenziano [this message]
2017-03-14 17:18 ` [PATCH] drm/i915: Extend rpm wakelock during i915_handle_error() Chris Wilson
2017-03-14 17:24 ` Michel Thierry
2017-03-15 15:45 ` Chris Wilson
2017-03-15 8:32 ` ✗ Fi.CI.BAT: failure for drm/i915: get a runtime PM ref in i915_wedged_set (rev2) Patchwork
2017-03-15 8:44 ` Patchwork
2017-03-15 8:50 ` ✓ 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=ffe047e5-6705-baff-af73-30a40c65221f@intel.com \
--to=antonio.argenziano@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michel.thierry@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox