From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [PATCH] drm/i915: Limit calling mark-busy only for potential scanouts Date: Tue, 8 May 2012 15:05:26 +0200 Message-ID: <20120508130526.GM4802@phenom.ffwll.local> References: <20120503143407.GH4983@phenom.ffwll.local> <1336056477-12230-1-git-send-email-chris@chris-wilson.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ey0-f177.google.com (mail-ey0-f177.google.com [209.85.215.177]) by gabe.freedesktop.org (Postfix) with ESMTP id C20309ED7B for ; Tue, 8 May 2012 06:04:17 -0700 (PDT) Received: by eaak13 with SMTP id k13so1772691eaa.36 for ; Tue, 08 May 2012 06:04:16 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1336056477-12230-1-git-send-email-chris@chris-wilson.co.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org 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 Queued for -next, thanks for the patch. -Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48