From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Restrict GPU boost to the RCS engine
Date: Wed, 17 Dec 2014 18:02:06 +0100 [thread overview]
Message-ID: <20141217170206.GU2711@phenom.ffwll.local> (raw)
In-Reply-To: <20141217151205.GI26498@nuc-i3427.alporthouse.com>
On Wed, Dec 17, 2014 at 03:12:05PM +0000, Chris Wilson wrote:
> On Thu, Jun 12, 2014 at 10:28:55AM +0100, Chris Wilson wrote:
> > Make the assumption that media workloads are not as latency sensitive
> > for __wait_seqno, and that upclocking the GPU does not affect the BLT
> > engine. Under that assumption, we only wait to forcibly upclock the GPU
> > when we are stalling for results from the render pipeline.
>
> For reference, the BLT does depend upon the gpu frequency (and acts as
> a media source of busyness), and to lesser extent the ring/memory bw,
> also controlled as a side-effect of gpu frequency.
>
> Tested on ivb, i7-3720QM
Since the patch landed already, can you please submit a fixup to add the
|| ring == BLT with Deepak on cc so he can review it?
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-17 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 9:28 [PATCH] drm/i915: Restrict GPU boost to the RCS engine Chris Wilson
2014-06-12 9:32 ` Daniel Vetter
2014-06-21 3:13 ` Deepak S
2014-06-24 11:52 ` Deepak S
2014-07-07 9:05 ` Daniel Vetter
2014-07-09 4:39 ` Deepak S
2014-07-08 6:38 ` Chris Wilson
2014-07-08 8:25 ` Daniel Vetter
2014-12-17 15:12 ` Chris Wilson
2014-12-17 17:02 ` Daniel Vetter [this message]
2014-12-17 17:37 ` Chris Wilson
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=20141217170206.GU2711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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