From: Chris Wilson <chris@chris-wilson.co.uk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Keith Packard <keithp@keithp.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Greg Kroah-Hartman <greg@kroah.com>,
dri-devel@lists.freedesktop.org, linux-pm@vger.kernel.org
Subject: Re: Massive power regression going 3.4->3.5
Date: Tue, 31 Jul 2012 09:28:57 +0100 [thread overview]
Message-ID: <1343723344_20808@CP5-2952> (raw)
In-Reply-To: <1343722002.3516.1.camel@dabdike.int.hansenpartnership.com>
On Tue, 31 Jul 2012 09:06:42 +0100, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> Actually, bad news: it looks like the problem is drm:
>
> on 3.5 killing X causes idle power to go 14W -> 5.9W
> on 3.4.6 killing X causes idle power to go 6.8W -> 5.7W
The files that will be the most interesting to compare at first are:
/sys/kernel/debug/dri/0/i915_drpc_info
/sys/kernel/debug/dri/0/i915_cur_delayinfo
/sys/kernel/debug/dri/0/i915_fbc_status
However if it was simple regression in drm, then the bisect would have
continued to work despite the merge point jumping between 3.4 and 3.5,
right?
Thanks,
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-31 8:29 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 [this message]
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
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=1343723344_20808@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=keithp@keithp.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