From: Daniel Vetter <daniel@ffwll.ch>
To: Jordan Justen <jordan.l.justen@intel.com>
Cc: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add GPGPU_THREADS_DISPATCHED to the register whitelist
Date: Tue, 16 Dec 2014 10:37:28 +0100 [thread overview]
Message-ID: <20141216093728.GS2711@phenom.ffwll.local> (raw)
In-Reply-To: <20141215195024.15800.6408@jljusten-ivy>
On Mon, Dec 15, 2014 at 11:50:24AM -0800, Jordan Justen wrote:
> On 2014-12-15 06:59:16, Daniel Vetter wrote:
> > On Thu, Dec 11, 2014 at 03:48:20PM -0800, Ben Widawsky wrote:
> > > On Thu, Dec 11, 2014 at 01:28:09PM -0800, Jordan Justen wrote:
> > > > This will allow us to read the number of dispatched compute threads
> > > > for GL_ARB_pipeline_statistics_query.
> >
> > Just so we have all the formally required pieces: Can you please supply a
> > link to the mesa code for this? I'm a bit behind on reading mesa-dev.
>
> This is an early hacked version of mesa that uses the register:
> http://cgit.freedesktop.org/~jljusten/mesa/log/?h=cs%2bps
>
> I veried reading the register with the modified mesa and a piglit
> test. I first tested with the cmd parser disabled, and then with this
> patch.
>
> I'm waiting for the initial GL_ARB_pipeline_statistics_query extension
> (without CS support) to make it upstream in mesa before finishing and
> sending out the CS support.
>
> If this is in next, can I proceed to upstream a mesa patch that
> depends on version 3 of the command parser? Or, should I wait until
> this makes it fully upstream?
If we go super strict with rule abi is locked down when I tag
drm-intel-next at the end of this weeek. But that's hair-splitting. So
yeah, as soon as all the mesa depencies have landed you can just go ahead
with your patches.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-12-16 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 21:28 [PATCH] drm/i915: Add GPGPU_THREADS_DISPATCHED to the register whitelist Jordan Justen
2014-12-11 23:48 ` Ben Widawsky
2014-12-15 14:59 ` Daniel Vetter
2014-12-15 19:50 ` Jordan Justen
2014-12-16 9:37 ` Daniel Vetter [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=20141216093728.GS2711@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jordan.l.justen@intel.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 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.