From: "Gupta, Sourab" Subject: Re: [PATCH 2/2] drm/i915/vlv: Enabling the TLB invalidate bit in GFX Mode register Date: Fri, 21 Mar 2014 13:31:56 +0000 Message-ID: <1395408752.19358.38.camel@sourabgu-desktop> References: <20140207123128.GJ5360@nuc-i3427.alporthouse.com> <1395405304-7012-1-git-send-email-sourab.gupta@intel.com> <1395405304-7012-2-git-send-email-sourab.gupta@intel.com> <20140321125854.GB18789@nuc-i3427.alporthouse.com> <1395407389.19358.33.camel@sourabgu-desktop> <20140321131753.GC18789@nuc-i3427.alporthouse.com> 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 867AF6E325 for ; Fri, 21 Mar 2014 06:34:30 -0700 (PDT) In-Reply-To: <20140321131753.GC18789@nuc-i3427.alporthouse.com> Content-Language: en-US Content-ID: <434B6B6D3DA538449AABCCDC82430737@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Chris Wilson Cc: "Goel, Akash" , Daniel Vetter , "intel-gfx@lists.freedesktop.org" , "Wilson, Chris" List-Id: intel-gfx@lists.freedesktop.org On Fri, 2014-03-21 at 13:17 +0000, Chris Wilson wrote: > On Fri, Mar 21, 2014 at 01:09:12PM +0000, Gupta, Sourab wrote: > > On Fri, 2014-03-21 at 12:58 +0000, Chris Wilson wrote: > > > On Fri, Mar 21, 2014 at 06:05:04PM +0530, sourab.gupta@intel.com wrote: > > > > From: Akash Goel > > > > > > > > This patch Enables the bit for TLB invalidate in GFX Mode register. > > > > > > > > According to bspec, When enabled this bit limits the invalidation > > > > of the TLB only to batch buffer boundaries, to pipe_control > > > > commands which have the TLB invalidation bit set and sync flushes. > > > > If disabled, the TLB caches are flushed for every full flush of > > > > the pipeline. > > > > > > So why do we want to not disable it? > > > -Chris > > > > > Hi Chris, > > As per the description, enabling this bit will make the TLB invalidation > > more optimal. Otherwise, TLB invalidation will happen for every full > > pipeline flush. Thats why we are enabling this bit. > > You are not enabling the bit either, you simply do not disable it. > -Chris > Hi Chris, According to spec, the default value of this bit will be 1 after reset. So, we are letting the default value remain as 1 and not disabling it. Probably the commit message should have better reflected this as 'not resetting the bit for TLB invalidate from its default value of 1'. If required, we can explicitly set the value to 1 (without assuming any defaults). Regards, Sourab