From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Limit calling mark-busy only for potential scanouts
Date: Tue, 8 May 2012 15:05:26 +0200 [thread overview]
Message-ID: <20120508130526.GM4802@phenom.ffwll.local> (raw)
In-Reply-To: <1336056477-12230-1-git-send-email-chris@chris-wilson.co.uk>
On Thu, May 03, 2012 at 03:47:57PM +0100, Chris Wilson wrote:
> The principle of intel_mark_busy() is that we want to spot the
> transition of when the display engine is being used in order to bump
> powersaving modes and increase display clocks. As such it is only
> important when the display is changing, i.e. when rendering to the
> scanout or other sprite/plane, and these are characterised by being
> pinned.
>
> v2: Mark the whole device as busy on execbuffer and pageflips as well
> and rebase against dinq for the minor bug fix to be immediately
> applicable.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-05-08 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 11:35 [PATCH 1/2] drm/i915: Avoid concurrent access when marking the device as idle/busy Chris Wilson
2012-05-03 11:35 ` [PATCH 2/2] drm/i915: Limit calling mark-busy only for potential scanouts Chris Wilson
2012-05-03 14:34 ` Daniel Vetter
2012-05-03 14:47 ` [PATCH] " Chris Wilson
2012-05-08 13:05 ` Daniel Vetter [this message]
2012-05-08 13:14 ` [PATCH 1/2] drm/i915: Avoid concurrent access when marking the device as idle/busy Daniel Vetter
2012-05-09 11:39 ` [PATCH] " 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=20120508130526.GM4802@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