From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH] drm/i915: Add aub debug support for kernel Date: Sun, 07 Nov 2010 15:33:15 +0000 Message-ID: <5b55a1$ijdg71@fmsmga002.fm.intel.com> References: <1288689096-23230-1-git-send-email-yuanhan.liu@intel.com> <849307$a7if4n@azsmga001.ch.intel.com> <5b55a1$ij0t3g@fmsmga002.fm.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTP id 7BF3E9E912 for ; Sun, 7 Nov 2010 07:33:18 -0800 (PST) In-Reply-To: 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: Liu Aleaxander Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Sun, 7 Nov 2010 23:04:40 +0800, Liu Aleaxander wrote: > But back to that issue again, how can we get the data of register > read/write at the KMS phase. i195:* trace event does exist only when > i915 module is loaded. Meanwhile, the KMS phase is passed by when you > are trying to enable i915_reg_rw event. > > Chris, your ideas? The hacky approach is a module parameter (i915.trace_load=1) that we parse in i915_init() and enable the trace points manually. I remember this being possible, once upon a time... I'll keep digging to see how we can do it today. The long term solution is to ask for a generic method to enable module tracepoints upon module load. -Chris -- Chris Wilson, Intel Open Source Technology Centre