From: Alex Williamson <alex.williamson@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Tina Zhang <tina.zhang@intel.com>,
chris@chris-wilson.co.uk, joonas.lahtinen@linux.intel.com,
zhenyuw@linux.intel.com, zhiyuan.lv@intel.com,
zhi.a.wang@intel.com, kevin.tian@intel.com, daniel@ffwll.ch,
kwankhede@nvidia.com, hang.yuan@intel.com,
intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v18 0/6] drm/i915/gvt: Dma-buf support for GVT-g
Date: Wed, 15 Nov 2017 15:48:06 -0700 [thread overview]
Message-ID: <20171115154806.76917bc4@t450s.home> (raw)
In-Reply-To: <20171115104900.kcjpva33wfo7aurn@sirius.home.kraxel.org>
On Wed, 15 Nov 2017 11:49:00 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:
> On Wed, Nov 15, 2017 at 05:11:49PM +0800, Tina Zhang wrote:
> > v17->v18:
> > 1) unmap vgpu's opregion when destroying vgpu.
> > 2) update comments for VFIO_DEVICE_GET_GFX_DMABUF. (Alex)
>
> > This patch set adds the dma-buf support for intel GVT-g.
> >
> > dma-buf is an uniform mechanism to share DMA buffers across different
> > devices and subsystems. dma-buf for intel GVT-g is mainly used to share
> > the vgpu's framebuffer to userspace to leverage userspace graphics stacks
> > to render the framebuffer to the display monitor.
> >
> > The main idea is that we create a gem object and set vgpu's framebuffer as
> > its backing storage. Then, export a dma-buf associated with this gem object.
> > With the fd of this dma-buf, userspace can directly handle this buffer.
> >
> > This patch set can be tried with the following example:
> > git://git.kraxel.org/qemu branch: work/intel-vgpu
> >
> > A topic branch with the latest patch set is:
> > https://github.com/intel/gvt-linux.git branch: topic/dmabuf
>
> Tested-by: Gerd Hoffmann <kraxel@redhat.com>
Hi Gerd,
Can you share the xml snippets required for the VM to make this work?
Last I tried I couldn't get the display/video/hostdev configuration to
get any enhanced behavior through the dmabuf. Thanks,
Alex
next prev parent reply other threads:[~2017-11-15 22:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 9:11 Tina Zhang
2017-11-15 9:11 ` [PATCH v18 1/6] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-11-15 9:11 ` [PATCH v18 2/6] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-11-15 9:11 ` [PATCH v18 3/6] drm/i915/gvt: Add " Tina Zhang
2017-11-15 9:11 ` [PATCH v18 4/6] drm/i915/gvt: Add opregion support Tina Zhang
2017-11-15 9:11 ` [PATCH v18 5/6] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-11-15 10:47 ` Gerd Hoffmann
2017-11-15 18:48 ` Alex Williamson
2017-11-16 3:21 ` Zhenyu Wang
2017-11-16 4:11 ` Alex Williamson
2017-11-18 15:30 ` Alex Williamson
2017-11-18 17:59 ` Kirti Wankhede
2017-11-18 18:13 ` Alex Williamson
2017-11-15 9:11 ` [PATCH v18 6/6] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-11-15 10:49 ` [PATCH v18 0/6] drm/i915/gvt: Dma-buf " Gerd Hoffmann
2017-11-15 22:48 ` Alex Williamson [this message]
2017-11-16 9:33 ` Gerd Hoffmann
2017-11-23 6:12 ` Zhenyu Wang
2017-11-23 7:51 ` Zhang, Tina
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=20171115154806.76917bc4@t450s.home \
--to=alex.williamson@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=hang.yuan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®