On Wed, 15 Feb 2012 12:16:20 -0800
Eric Anholt wrote:
> On Tue, 14 Feb 2012 22:09:15 +0100, Ben Widawsky wrote:
> > Extend the flag parameter to support the context id (from the create
> > IOCTL) so that userspace can associate a context with the batchbuffer.
> >
> > Signed-off-by: Ben Widawsky
On Wed, 15 Feb 2012 21:00:16 +0100
Ben Widawsky wrote:
> On Wed, 15 Feb 2012 11:55:56 -0800
> Eric Anholt wrote:
>
> > On Tue, 14 Feb 2012 22:09:15 +0100, Ben Widawsky wrote:
> > > Extend the flag parameter to support the context id (from the create
> > > IOCTL) so that userspace can associate
On Tue, 14 Feb 2012 22:09:15 +0100, Ben Widawsky wrote:
> Extend the flag parameter to support the context id (from the create
> IOCTL) so that userspace can associate a context with the batchbuffer.
>
> Signed-off-by: Ben Widawsky
> @@ -1270,6 +1272,14 @@ i915_gem_do_execbuffer(struct drm_devi
On Wed, 15 Feb 2012 11:55:56 -0800
Eric Anholt wrote:
> On Tue, 14 Feb 2012 22:09:15 +0100, Ben Widawsky wrote:
> > Extend the flag parameter to support the context id (from the create
> > IOCTL) so that userspace can associate a context with the batchbuffer.
> >
> > Signed-off-by: Ben Widawsky
On Tue, 14 Feb 2012 22:09:15 +0100, Ben Widawsky wrote:
> Extend the flag parameter to support the context id (from the create
> IOCTL) so that userspace can associate a context with the batchbuffer.
>
> Signed-off-by: Ben Widawsky
> /** Resets the SO write offset registers for transform feedb
On Tue, Feb 14, 2012 at 19:09, Ben Widawsky wrote:
> Extend the flag parameter to support the context id (from the create
> IOCTL) so that userspace can associate a context with the batchbuffer.
>
This seems to be the easiest way to add the support for contexts. So at
least for me, I think this
Extend the flag parameter to support the context id (from the create
IOCTL) so that userspace can associate a context with the batchbuffer.
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/i915_drv.h|2 ++
drivers/gpu/drm/i915/i915_gem_execbuffer.c | 26