public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Ben Widawsky <ben@bwidawsk.net>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] libdrm_intel: Add support for userptr objects
Date: Mon, 12 May 2014 18:00:37 +0200	[thread overview]
Message-ID: <20140512160037.GG25056@phenom.ffwll.local> (raw)
In-Reply-To: <20140509053011.GE3443@nuc-i3427.alporthouse.com>

On Fri, May 09, 2014 at 06:30:11AM +0100, Chris Wilson wrote:
> On Thu, May 08, 2014 at 05:10:24PM -0700, Ben Widawsky wrote:
> > On Wed, Feb 26, 2014 at 04:41:41PM +0000, Tvrtko Ursulin wrote:
> > > +struct drm_i915_gem_userptr {
> > > +	__u64 user_ptr;
> > > +	__u64 user_size;
> > > +	__u32 flags;
> > > +#define I915_USERPTR_READ_ONLY 0x1
> > > +#define I915_USERPTR_UNSYNCHRONIZED 0x80000000
> > > +	/**
> > > +	* Returned handle for the object.
> > > +	*
> > > +	* Object handles are nonzero.
> > > +	*/
> > > +	__u32 handle;
> > > +};
> > > +
> > 
> > Oh yeah. I want a ctx_id here as well. Chris, any objection to adding
> > this?
> 
> What for? bo are file-scoped not context-scoped.

I think what Ben actually wants is a ctx_id in the soft-pin ioctl. Makes
his mirrored ppgtt POC a 2 ioctl thing, but the resulting orthogonality of
interfaces is imo something much to be preferred. Since we still need real
bos for scanout targets and similar, and I'm going to rip everyone's head
off if we do that by shmem-mapping+userptr ;-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-05-12 16:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:41 [RFC] libdrm_intel: Add support for userptr objects Tvrtko Ursulin
2014-05-01 18:47 ` Ben Widawsky
2014-05-02 10:27   ` Tvrtko Ursulin
2014-05-02 17:15     ` Ben Widawsky
2014-05-05  9:35       ` Daniel Vetter
2014-05-07 10:33       ` Tvrtko Ursulin
2014-05-09  0:10 ` Ben Widawsky
2014-05-09  5:30   ` Chris Wilson
2014-05-12 16:00     ` Daniel Vetter [this message]
2014-06-19 11:13 ` Damien Lespiau
2014-06-19 11:27   ` Damien Lespiau
2014-07-09 13:08   ` Tvrtko Ursulin
2014-07-09 13:16     ` Damien Lespiau
2014-07-09 14:25       ` Daniel Vetter
2014-07-09 14:47         ` Chris Wilson
2014-06-19 14:52 ` [PATCH] intel: " Tvrtko Ursulin
2014-09-17 11:26   ` Damien Lespiau

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=20140512160037.GG25056@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --cc=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox