From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [PATCH 4/6] drm/i915: simplify i915_reset a bit Date: Wed, 25 Apr 2012 09:18:21 -0700 Message-ID: <20120425091821.19fc7808@jbarnes-desktop> References: <1335355033-3854-1-git-send-email-daniel.vetter@ffwll.ch> <1335355033-3854-5-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 oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by gabe.freedesktop.org (Postfix) with SMTP id 0A0BC9E754 for ; Wed, 25 Apr 2012 09:18:27 -0700 (PDT) In-Reply-To: <1335355033-3854-5-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: Daniel Vetter Cc: Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org On Wed, 25 Apr 2012 13:57:11 +0200 Daniel Vetter wrote: > - need_display is always true, scrap it. > - don't reacquire the mutex to do nothing after having restored the > gem state. > Actually I think we generally *don't* need to reset display. It's currently there just because we haven't tried reset handling without it. But not resetting display would make resets a little less visible, which would be nice. Now that you have a nice test setup, can you try testing without the display engine bit set (i.e. only reset render and media at hang time)? -- Jesse Barnes, Intel Open Source Technology Center