From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>,
"Zhang, Tina" <tina.zhang@intel.com>
Cc: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
"Wang, Zhi A" <zhi.a.wang@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"kwankhede@nvidia.com" <kwankhede@nvidia.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v15 5/7] vfio: ABI for mdev display dma-buf operation
Date: Wed, 11 Oct 2017 08:27:14 +0200 [thread overview]
Message-ID: <1507703234.31518.5.camel@redhat.com> (raw)
In-Reply-To: <20171010201824.25d2ae79@t450s.home>
Hi,
> No, the parameter wouldn't be a char, you'd use an __u32 for the
> dmabuf_id. I'm just referencing the structure of the GET_DEVICE_FD
> as
> an ioctl which returns an fd through the return value and takes a
> single parameter. I don't mean to imply matching the type of that
> parameter.
> Gerd, what are your thoughts on that, it'd make it slightly
> easier to call GET_GFX_DMABUF, but it limits us to file descriptor
> for
> the dmabuf whereas with a flag and expandable structure we could use
> some future mechanism to return the dmabuf to userspace.
It's fine with me.
The point of using fd's to refer to dmabufs is that they can be passed
around easily, so I doubt this is going to change.
cheers,
Gerd
next prev parent reply other threads:[~2017-10-11 6:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 9:50 [PATCH v15 0/7] drm/i915/gvt: Dma-buf support for GVT-g Tina Zhang
2017-10-10 9:50 ` [PATCH v15 1/7] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-10-10 9:50 ` [PATCH v15 2/7] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 9:50 ` [PATCH v15 3/7] drm/i915/gvt: Add " Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 9:50 ` [PATCH v15 4/7] drm/i915/gvt: Add opregion support Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-11 4:29 ` Du, Changbin
2017-10-11 4:29 ` Du, Changbin
2017-10-10 9:50 ` [PATCH v15 5/7] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 14:07 ` Gerd Hoffmann
2017-10-10 19:16 ` Alex Williamson
2017-10-11 1:46 ` Zhang, Tina
2017-10-11 1:46 ` Zhang, Tina
2017-10-11 2:18 ` Alex Williamson
2017-10-11 2:18 ` Alex Williamson
2017-10-11 6:27 ` Gerd Hoffmann [this message]
2017-10-10 9:50 ` [PATCH v15 6/7] drm/i915: Introduce GEM proxy Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 10:58 ` Joonas Lahtinen
2017-10-10 13:02 ` [Intel-gfx] " Joonas Lahtinen
2017-10-11 1:54 ` Zhang, Tina
2017-10-10 9:50 ` [PATCH v15 7/7] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-10-10 9:50 ` Tina Zhang
2017-10-10 10:05 ` ✗ Fi.CI.BAT: failure for drm/i915/gvt: Dma-buf " Patchwork
2017-10-10 14:06 ` [PATCH v15 0/7] " Gerd Hoffmann
2017-10-10 14:06 ` Gerd Hoffmann
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=1507703234.31518.5.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
--cc=zhiyuan.lv@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.