From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 1/2] drm/i915: more forcewake lock error info Date: Wed, 22 Jun 2011 18:00:43 +0100 Message-ID: References: <1308761701-1751-1-git-send-email-ben@bwidawsk.net> <1308761701-1751-2-git-send-email-ben@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga14.intel.com (mga14.intel.com [143.182.124.37]) by gabe.freedesktop.org (Postfix) with ESMTP id 381A99F758 for ; Wed, 22 Jun 2011 10:00:47 -0700 (PDT) In-Reply-To: <1308761701-1751-2-git-send-email-ben@bwidawsk.net> 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 , intel-gfx@lists.freedesktop.org Cc: Alexander Zhaunerchyk List-Id: intel-gfx@lists.freedesktop.org On Wed, 22 Jun 2011 09:55:00 -0700, Ben Widawsky wrote: > Get some more useful info for debugging backtraces on forcewake > problems. Appropriate debug flags will be required for the drm module. Wouldn't it be neater to pass the reg down to gen6_gt_force_wake_get() so that we only have a single debug message and not an additional one for every inlined read/write? -Chris -- Chris Wilson, Intel Open Source Technology Centre