From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5 v2] [RFC] GTT vtable
Date: Wed, 23 Jan 2013 13:07:47 +0000 [thread overview]
Message-ID: <20130123130747.GC7455@cantiga.alporthouse.com> (raw)
In-Reply-To: <CAKMK7uHD1CukbapvP1+0VGRbXp9G-AfY0p_qdOJq_SAGzjs1LQ@mail.gmail.com>
On Wed, Jan 23, 2013 at 12:39:01PM +0100, Daniel Vetter wrote:
> On Wed, Jan 23, 2013 at 12:03 PM, Chris Wilson <chris@chris-wilson.co.uk> 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
prev parent reply other threads:[~2013-01-23 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 22:10 [PATCH 0/5 v2] [RFC] GTT vtable Ben Widawsky
2013-01-21 22:10 ` [PATCH 1/5] drm/i915: Create a vtable for i915 gtt Ben Widawsky
2013-01-21 22:10 ` [PATCH 2/5] drm/i915: Resume dissecting intel_gtt Ben Widawsky
2013-01-21 22:10 ` [PATCH 3/5] drm/i915: Extract gtt stolen calculations Ben Widawsky
2013-01-21 22:10 ` [PATCH 4/5] drm/i915: Extract clear_range to gtt_ops Ben Widawsky
2013-01-21 22:10 ` [PATCH 5/5] drm/i915: Extract bind object Ben Widawsky
2013-01-23 11:03 ` [PATCH 0/5 v2] [RFC] GTT vtable Chris Wilson
2013-01-23 11:39 ` Daniel Vetter
2013-01-23 13:07 ` Chris Wilson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130123130747.GC7455@cantiga.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.