From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Siluvery, Arun" Subject: Re: [PATCH] igt/gem_workarounds: igt to test workaround registers Date: Wed, 27 Aug 2014 17:17:11 +0100 Message-ID: <53FE0487.2010607@linux.intel.com> References: <1409061028-5087-1-git-send-email-arun.siluvery@linux.intel.com> <20140827155016.GW15520@phenom.ffwll.local> <20140827155911.GM13629@nuc-i3427.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id DDD2C6E042 for ; Wed, 27 Aug 2014 09:17:18 -0700 (PDT) In-Reply-To: <20140827155911.GM13629@nuc-i3427.alporthouse.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 , Daniel Vetter , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On 27/08/2014 16:59, Chris Wilson wrote: > On Wed, Aug 27, 2014 at 05:50:16PM +0200, Daniel Vetter wrote: >> On Tue, Aug 26, 2014 at 02:50:28PM +0100, Arun Siluvery wrote: >>> Some of the workarounds are lost followed by a gpu reset, suspend/resume; >>> this patch adds a test which compares register state before and after >>> the test scenario. >>> >>> This test currently verifies only bdw workarounds. > > The existing tool didn't need kernel help (other than forcewake). Why > was that not used as a starting point? > -Chris > Do you mean intel_reg_checker()? This new test uses kernel help to get the initial state of workarounds which are exported to debugfs. We could add this known state to the test itself but Daniel is not ok with that. debugfs part is only added to support the test. regards Arun