From: Eric Anholt <eric@anholt.net>
To: Paul Berry <stereotype441@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] intel: Add the ability to supply annotations for .aub files.
Date: Thu, 10 May 2012 09:25:22 -0700 [thread overview]
Message-ID: <87havom2a5.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <CA+yLL67tuGurrRempGKAGnAogmQ3e3zn8iqqJ7QqPJ31oL_pmw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1568 bytes --]
On Thu, 10 May 2012 06:43:54 -0700, Paul Berry <stereotype441@gmail.com> wrote:
> On 9 May 2012 20:07, Eric Anholt <eric@anholt.net> wrote:
>
> > On Mon, 7 May 2012 14:31:51 -0700, Paul Berry <stereotype441@gmail.com>
> > wrote:
> > > This patch adds a new function,
> > > drm_intel_bufmgr_gem_set_aub_annotations(), which can be used to
> > > annotate the type and subtype of data stored in various sections of
> > > each buffer. This data is used to populate type and subtype fields
> > > when generating the .aub file, which improves the ability of later
> > > debugging tools to analyze the contents of the .aub file.
> > >
> > > If drm_intel_bufmgr_gem_set_aub_annotations() is not called, then we
> > > fall back to the old set of annotations (annotate the portion of the
> > > batchbuffer that is executed as AUB_TRACE_TYPE_BATCH, and everything
> > > else as AUB_TRACE_TYPE_NOTYPE).
> >
> > This looks better than the interface I was thinking of. Only real
> > nitpick note is that the style in this file is tab indents, rather than
> > 8 spaces, same as linux kernel and 2d driver style. (I have since been
> > convinced that 8 spaces is superior, but a mix is worse).
> >
>
> Ok. Are there any plans to switch drm over to spaces or are we stuck with
> tabs forever?
Our project as a whole includes work on the linux kernel, and most
people working on libdrm are also working on the kernel. As far as I'm
concerned, having a different style between them would be worse than the
minor benefit of having diffs look nicer.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2012-05-10 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 21:31 [PATCH 1/2] intel: Add the ability to supply annotations for .aub files Paul Berry
2012-05-07 21:31 ` [PATCH 2/2] configure: Bump version for 2.4.34 Paul Berry
2012-05-10 3:08 ` Eric Anholt
2012-05-10 13:44 ` Paul Berry
2012-05-10 16:23 ` Eric Anholt
2012-05-10 3:07 ` [PATCH 1/2] intel: Add the ability to supply annotations for .aub files Eric Anholt
2012-05-10 13:43 ` Paul Berry
2012-05-10 16:25 ` Eric Anholt [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=87havom2a5.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stereotype441@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox