From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 0/5 v2] [RFC] GTT vtable Date: Wed, 23 Jan 2013 13:07:47 +0000 Message-ID: <20130123130747.GC7455@cantiga.alporthouse.com> References: <1358806236-1143-1-git-send-email-ben@bwidawsk.net> <20130123110321.GB7455@cantiga.alporthouse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by gabe.freedesktop.org (Postfix) with ESMTP id 598E4E5D25 for ; Wed, 23 Jan 2013 05:07:54 -0800 (PST) Content-Disposition: inline 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: Daniel Vetter Cc: Ben Widawsky , intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Wed, Jan 23, 2013 at 12:39:01PM +0100, Daniel Vetter wrote: > On Wed, Jan 23, 2013 at 12:03 PM, Chris Wilson wrote: > > On Mon, Jan 21, 2013 at 02:10:31PM -0800, Ben Widawsky wrote: > >> Elaborating a bit more on what we can do with the vtable... still hoping > >> to get feedback. > > > > Multiple layers of identical abstraction, just what we like! > > > > One thing that we lost in this switch is a small string identifying the > > chipset. When reading through a dmesg it is very handy to the GPU name > > in there, and we may as well print the pci-id. > > i915_dump_device_info not good enough? No, it's a keyword I use to familarise myself and sanity check random dmesgs attached to bug reports. -Chris -- Chris Wilson, Intel Open Source Technology Centre