From: Jani Nikula <jani.nikula@linux.intel.com>
To: "O'Rourke, Tom" <Tom.O'Rourke@intel.com>"O'Rourke,
Tom" <Tom.O'Rourke@intel.com>, Ben Widawsky <ben@bwidawsk.net>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/bdw: Use timeout mode for RC6 on bdw
Date: Wed, 02 Jul 2014 14:06:17 +0300 [thread overview]
Message-ID: <877g3wf2ae.fsf@intel.com> (raw)
In-Reply-To: <411E5DC12A51ED4CB1159E14310E532B9D8D5CA5@FMSMSX119.amr.corp.intel.com>
On Tue, 01 Jul 2014, "O'Rourke, Tom" <Tom.O'Rourke@intel.com> wrote:
>>>From: Ben Widawsky [mailto:ben@bwidawsk.net]
>>>Sent: Friday, June 20, 2014 9:43 AM
>>>On Wed, Apr 09, 2014 at 11:44:06AM -0700, Tom O'Rourke wrote:
>>>> Higher RC6 residency is observed using timeout mode instead of EI
>>>> mode. This applies to Broadwell only.
>>>> The difference is particularly noticeable with video playback.
>>>>
>>>> Issue: VIZ-3778
>>>> Change-Id: I62bb12e21caf19651034826b45cde7f73a80938d
>>>> Signed-off-by: Tom O'Rourke <Tom.O'Rourke@intel.com>
>>>
>>>
>>>Now that CHV is out, does it apply there too?
>>>Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
>>>
>>>[snip]
>>>
>>>
>>>--
>>>Ben Widawsky, Intel Open Source Technology Center
>>[TOR:] For CHV, we expect timeout mode will provide benefit on some pre-
>>production steppings and no benefit on the production stepping.
>
> [TOR:] Can we get this patch merged now that Ben has reviewed?
Pushed to dinq, thanks for the patch and review.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2014-07-02 11:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 18:44 [PATCH] drm/i915/bdw: Use timeout mode for RC6 on bdw Tom O'Rourke
2014-04-09 20:02 ` Daniel Vetter
2014-04-09 22:36 ` Ben Widawsky
2014-04-10 20:29 ` O'Rourke, Tom
2014-04-11 9:00 ` Daniel Vetter
2014-04-12 5:56 ` Ben Widawsky
2014-04-30 5:31 ` Ben Widawsky
2014-04-30 20:34 ` Kristen Carlson Accardi
2014-04-30 20:41 ` Ben Widawsky
2014-04-30 21:03 ` Imre Deak
2014-04-30 21:14 ` Kristen Carlson Accardi
2014-05-01 22:35 ` Ben Widawsky
2014-05-30 23:30 ` O'Rourke, Tom
2014-06-02 8:26 ` Daniel Vetter
2014-06-02 21:51 ` O'Rourke, Tom
2014-06-03 7:38 ` Daniel Vetter
2014-06-09 20:50 ` O'Rourke, Tom
2014-06-20 16:42 ` Ben Widawsky
2014-06-20 19:01 ` O'Rourke, Tom
2014-07-01 1:19 ` O'Rourke, Tom
2014-07-02 11:06 ` Jani Nikula [this message]
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=877g3wf2ae.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Tom.O'Rourke@intel.com \
--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