From: Chris Wilson <chris@chris-wilson.co.uk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Greg Kroah-Hartman <greg@kroah.com>,
Ben Widawsky <ben@bwidawsk.net>,
dri-devel@lists.freedesktop.org, linux-pm@vger.kernel.org
Subject: Re: Massive power regression going 3.4->3.5
Date: Wed, 01 Aug 2012 10:14:01 +0100 [thread overview]
Message-ID: <1343812442_25294@CP5-2952> (raw)
In-Reply-To: <1343812043.2960.7.camel@dabdike.int.hansenpartnership.com>
On Wed, 01 Aug 2012 10:07:23 +0100, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> > Can you please login to the desktop, let it idle, record
> > /sys/kernel/debug/dri/0/i915_cur_delayinfo and .../i915_drpc_info.
> > Then trace-cmd record -e i915 sleep 10s, and follow up with a new pair
> > of /sys/kernel/debug/dri/0/i915_cur_delayinfo and .../i915_drpc_info.
> >
> > This will let us see whether the pm counters are truly advancing and
> > what activity the driver is performing whilst idle.
>
> With or without i915_semaphore=0?
With semaphores enabled so that we can see if they are active during the
idle period or if merely having used them at some point is enough to
trigger the issue. And to see if the pm counters bear any relation to
reality.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-01 9:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1343477958.2891.6.camel@dabdike.int.hansenpartnership.com>
[not found] ` <1343557599.2745.1.camel@dabdike.int.hansenpartnership.com>
[not found] ` <201207291544.26334.rjw@sisk.pl>
[not found] ` <201207292125.21376.rjw@sisk.pl>
[not found] ` <1343641574.2905.2.camel@dabdike.int.hansenpartnership.com>
2012-07-30 14:54 ` Massive power regression going 3.4->3.5 James Bottomley
2012-07-30 16:33 ` Keith Packard
2012-07-30 17:05 ` James Bottomley
2012-07-30 18:23 ` Keith Packard
2012-07-31 7:31 ` James Bottomley
2012-07-31 8:06 ` James Bottomley
2012-07-31 8:28 ` Chris Wilson
2012-07-31 9:37 ` James Bottomley
2012-07-31 9:54 ` Chris Wilson
2012-07-31 9:57 ` James Bottomley
2012-07-31 10:14 ` Chris Wilson
2012-07-31 19:24 ` Chris Wilson
2012-08-01 8:06 ` James Bottomley
2012-08-01 8:16 ` Chris Wilson
2012-08-01 8:45 ` James Bottomley
2012-08-01 8:58 ` Chris Wilson
2012-08-01 9:07 ` James Bottomley
2012-08-01 9:14 ` Chris Wilson [this message]
2012-08-01 9:38 ` James Bottomley
2012-08-01 10:06 ` Chris Wilson
2012-08-02 5:08 ` bwidawsk
2012-08-02 7:20 ` James Bottomley
2012-08-02 12:07 ` Ben Widawsky
2012-08-01 10:08 ` James Bottomley
2012-08-05 20:36 ` Daniel Vetter
2012-08-07 20:43 ` James Bottomley
2012-08-08 2:44 ` Ben Widawsky
2012-08-08 7:22 ` Daniel Vetter
2012-08-06 19:31 ` [PATCH] drm/i915: make forcewake work again Ben Widawsky
2012-08-07 17:56 ` [Intel-gfx] " Ben Widawsky
2012-07-31 14:27 ` Massive power regression going 3.4->3.5 Keith Packard
2012-07-31 15:09 ` James Bottomley
2012-07-31 15:36 ` Chris Wilson
2012-07-31 16:25 ` James Bottomley
2012-07-30 18:23 ` Adam Jackson
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=1343812442_25294@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ben@bwidawsk.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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