From: Chris Wilson Subject: Re: [PATCH 1/5] drm/i915: WARN_ON failed map_and_fenceable Date: Sat, 10 Aug 2013 09:43:48 +0100 Message-ID: <20130810084348.GC3561@cantiga.alporthouse.com> References: <1376111536-12461-1-git-send-email-benjamin.widawsky@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (s16502780.onlinehome-server.info [87.106.93.118]) by gabe.freedesktop.org (Postfix) with ESMTP id AE03CE5C75 for ; Sat, 10 Aug 2013 01:43:59 -0700 (PDT) Content-Disposition: inline In-Reply-To: <1376111536-12461-1-git-send-email-benjamin.widawsky@intel.com> 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: Ben Widawsky Cc: Intel GFX , Ben Widawsky List-Id: intel-gfx@lists.freedesktop.org On Fri, Aug 09, 2013 at 10:12:12PM -0700, Ben Widawsky wrote: > I just noticed in our code we don't really check the assertion, and > given some of the code I am changing in this area, I feel a WARN is very > nice to have. > > Signed-off-by: Ben Widawsky This is BUG() class. A WARN by itself here isn't going to prevent calamity, so cleanup and let userspace die gracefully. The alternative is random hw borkage (hopefully triggering an OOPS before it gets too far). -Chris -- Chris Wilson, Intel Open Source Technology Centre