From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: fix infinite loop at gen6_update_ring_freq
Date: Wed, 2 Apr 2014 09:26:42 +0200 [thread overview]
Message-ID: <20140402072642.GM7225@phenom.ffwll.local> (raw)
In-Reply-To: <1396391989-2244-4-git-send-email-przanoni@gmail.com>
On Tue, Apr 01, 2014 at 07:39:49PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> If I boot my Broadwell machine to X on a system with Mesa Gallium
> llvmpipe instead of i965, then kill X and try to run pm_pc8.c, when we
> disable PC8 and call gen6_update_ring_freq(), we will get stuck on an
> infinite loop because the frequencies are zero and the variables are
> unsigned. This happens because we never ran any batch, so we did not
> enable RC6, so the variables are zero. If I run gem_exec_nop before
> running pm_pc8, everything works as expected because gem_exec_nop
> makes RC6 be enabled.
>
> This commit should prevent the infinite loop, which IMHO is already a
> good reason to be merged, but it is not the proper fix to the "RC6 is
> not being enabled" problem.
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
This will be fixed (I hope at least) once we have the in-kernel 3d state
emission stuff.
But there's still a race when we go into runtime suspend right after
coming out of system resume. I think we need to grab a runtime pm
reference when we launch the delayed rps work and drop it once that has
run. Or at least we need to have a flush_delayed_work in the runtime pm
suspend function.
There's probably piles more stuff like this.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-04-02 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 22:39 [PATCH 0/3] BDW runtime PM fixes Paulo Zanoni
2014-04-01 22:39 ` [PATCH 1/3] drm/i915: only check for irqs_disabled when disabling LCPLL Paulo Zanoni
2014-04-02 7:28 ` Daniel Vetter
2014-04-01 22:39 ` [PATCH 2/3] drm/i915: Allow i915_pc8_status debug info on BDW Paulo Zanoni
2014-04-02 5:04 ` Ben Widawsky
2014-04-02 7:27 ` Daniel Vetter
2014-04-01 22:39 ` [PATCH 3/3] drm/i915: fix infinite loop at gen6_update_ring_freq Paulo Zanoni
2014-04-02 5:03 ` Ben Widawsky
2014-04-02 7:26 ` Daniel Vetter [this message]
2014-04-02 14:58 ` [PATCH 0/3] BDW runtime PM fixes Daniel Vetter
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=20140402072642.GM7225@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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