From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] libdrm_intel: Add support for userptr objects
Date: Wed, 9 Jul 2014 16:25:55 +0200 [thread overview]
Message-ID: <20140709142554.GY17271@phenom.ffwll.local> (raw)
In-Reply-To: <20140709131659.GC341@strange.amr.corp.intel.com>
On Wed, Jul 09, 2014 at 02:16:59PM +0100, Damien Lespiau wrote:
> On Wed, Jul 09, 2014 at 02:08:08PM +0100, Tvrtko Ursulin wrote:
> >
> > On 06/19/2014 12:13 PM, Damien Lespiau wrote:
> > >On Wed, Feb 26, 2014 at 04:41:41PM +0000, Tvrtko Ursulin wrote:
> > >>From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > >>
> > >>Allow userptr objects to be created and used via libdrm_intel.
> > >>
> > >>At the moment tiling and mapping to GTT aperture is not supported
> > >>due hardware limitations across different generations and uncertainty
> > >>about its usefulness.
> > >>
> > >>Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > >>---
> > >> include/drm/i915_drm.h | 16 +++++
> > >> intel/intel_bufmgr.c | 13 ++++
> > >> intel/intel_bufmgr.h | 5 ++
> > >> intel/intel_bufmgr_gem.c | 154 +++++++++++++++++++++++++++++++++++++++++++++-
> > >> intel/intel_bufmgr_priv.h | 12 +++-
> > >> 5 files changed, 198 insertions(+), 2 deletions(-)
> > >
> > >Apart from couple of remarks below I couldn't find anything that would
> > >prevent merging this. Well, except maybe that it'd be very nice to have
> > >some feedback from someone using it, we do have an API/ABI guarantee on
> > >libdrm after all.
> >
> > Looks like I've forgotten to reply to this. I did address the other
> > review comments and sent out a v2 back then.
> >
> > But for what users are concerned, apart from internal ones who have
> > been using this API for some years now, I don't know of any.
>
> Well, considering this is only a wrapper of an ioctl() already
> upstreamed, I'm inclined to just push it as is. Daniel any thoughts?
Since both igt and sna have their own wrappers and the beinget patch for
this hasn't surfaced yet we don't really have a public open-source user
for this yet. My understanding of Dave's stance is that we should hold off
with committing until this is requirement is fulfilled.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-09 14:25 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
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 [this message]
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=20140709142554.GY17271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=damien.lespiau@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