From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH] drm/i915: Set persistent-mode for SNB framebuffer compression Date: Mon, 04 Jul 2011 19:18:11 +0100 Message-ID: References: <20110703153251.GA13463@snipes.kumite> <1309782957-9978-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 mga02.intel.com (mga02.intel.com [134.134.136.20]) by gabe.freedesktop.org (Postfix) with ESMTP id 753519E8D1 for ; Mon, 4 Jul 2011 11:18:14 -0700 (PDT) In-Reply-To: <1309782957-9978-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: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, 4 Jul 2011 13:35:57 +0100, Chris Wilson wrote: > Persistent mode is intended for use with front-buffer rendering, such as > X, where it is necessary to detect writes to the scanout either by the > GPU or through the CPU's fence, and recompress the dirty regions on the > fly. (By comparison to the back-buffer rendering, the scanout is always > recompressed after a page-flip.) > > This fixes the missing rendering oft triggered in the past, but easily > reproduced by using mutter with sna, for which the current workaround is > to disable fbc entirely. Hah. Spoke too soon, actually testing it, it seems the fix was due to the little buglet in the first patch which had the effect of disabling FBC. Oh well, it was a nice idea. -Chris -- Chris Wilson, Intel Open Source Technology Centre