From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 0/6] gpu hangman support Date: Wed, 25 Apr 2012 13:42:42 +0100 Message-ID: <1335357799_47366@CP5-2952> References: <1335355033-3854-1-git-send-email-daniel.vetter@ffwll.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id F29E29E935 for ; Wed, 25 Apr 2012 05:43:24 -0700 (PDT) In-Reply-To: <1335355033-3854-1-git-send-email-daniel.vetter@ffwll.ch> 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 Graphics Development Cc: Daniel Vetter List-Id: intel-gfx@lists.freedesktop.org On Wed, 25 Apr 2012 13:57:07 +0200, Daniel Vetter wrote: > Hi all, > > In the light of the recent oops in the error state code I've resurrected my gpu > hangman and brushed it up a bit. Together with the hangman check in i-g-t (which > now also works a bit more reliable) we'll have a basic test of our hangcheck, > reset and error state infrastructure. My only real complaint, aside from plenty of good advice on colour selection, is the freeing of error state from within /debug/i915_gem_stop_rings. I think that is a limitation borne out of convenience, and would rather have a writable /debug/i915_error_state. -Chris -- Chris Wilson, Intel Open Source Technology Centre