From: Gerd Hoffmann <kraxel@redhat.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
intel-gvt-dev@lists.freedesktop.org, qemu-devel@nongnu.org,
Tina Zhang <tina.zhang@intel.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/7] vfio: add display support
Date: Thu, 22 Feb 2018 10:30:55 +0100 [thread overview]
Message-ID: <20180222093055.u34o2pp6twcx645f@sirius.home.kraxel.org> (raw)
In-Reply-To: <20180222064003.yzrcmh7hi6qvgcij@zhen-hp.sh.intel.com>
Hi,
> Nice! Seems to be the last missing gap for local spice with cursor
> dmabuf support, we'll do more testing on that for sure. Btw, another
> method might be to add direct cursor dmabuf passing for spice as gl
> output, is that correct way?
Passing on the cursor sprite needs the hotspot information, so spice
client can position the cursor correctly. I didn't got hotspot
information in my testing yet, but maybe the guest kernel was too old.
Is that supported meanwhile? If so, which kernel version is needed?
Spice already has support for setting pointers, we can simply use
that, at least initially. Doesn't use dma-bufs. If it turns out to be
a performance issue we can add support for using dma-bufs instead, but
that needs spice server changes.
> And really like to see dmabuf support could be in upstream soon. Do
> you have any predict for which qemu version?
I want have this in 2.12, at least the current, initial version.
Improved cursor support might take a little longer.
cheers,
Gerd
next prev parent reply other threads:[~2018-02-22 9:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 11:14 [Qemu-devel] [PATCH v4 0/7] vfio: add display support Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 1/7] linux-headers: update to 4.16-rc1 Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 2/7] standard-headers: add drm/drm_fourcc.h Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 3/7] ui/pixman: add qemu_drm_format_to_pixman() Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 4/7] qdev: add hotpluggable to DeviceState Gerd Hoffmann
2018-02-22 15:37 ` Gerd Hoffmann
2018-02-22 15:46 ` Peter Maydell
2018-02-22 16:59 ` Alex Williamson
2018-02-22 17:21 ` Peter Maydell
2018-02-23 3:14 ` Zhenyu Wang
2018-02-23 8:53 ` Gerd Hoffmann
2018-02-23 15:58 ` Alex Williamson
2018-02-26 8:23 ` Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 5/7] vfio/common: cleanup in vfio_region_finalize Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 6/7] vfio/display: core & wireup Gerd Hoffmann
2018-02-19 11:14 ` [Qemu-devel] [PATCH v4 7/7] vfio/display: adding region support Gerd Hoffmann
2018-02-19 22:16 ` [Qemu-devel] [PATCH v4 0/7] vfio: add display support Alex Williamson
2018-02-20 10:28 ` Gerd Hoffmann
2018-02-20 17:04 ` Gerd Hoffmann
2018-02-22 6:40 ` Zhenyu Wang
2018-02-22 9:30 ` Gerd Hoffmann [this message]
2018-02-23 2:42 ` Zhenyu Wang
2018-02-23 7:06 ` Zhang, Tina
2018-02-22 16:28 ` Alex Williamson
2018-02-23 9:05 ` Gerd Hoffmann
2018-02-26 8:35 ` Gerd Hoffmann
2018-02-26 20:59 ` Alex Williamson
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=20180222093055.u34o2pp6twcx645f@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@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;
as well as URLs for NNTP newsgroup(s).