From: Alex Williamson <alex.williamson@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, Tina Zhang <tina.zhang@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Kirti Wankhede <kwankhede@nvidia.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/7] vfio: add display support
Date: Thu, 22 Feb 2018 09:28:11 -0700 [thread overview]
Message-ID: <20180222092811.0a705b9e@w520.home> (raw)
In-Reply-To: <20180220102814.rtcvsrsdtdndcfez@sirius.home.kraxel.org>
On Tue, 20 Feb 2018 11:28:14 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:
> On Mon, Feb 19, 2018 at 03:16:49PM -0700, Alex Williamson wrote:
> > On Mon, 19 Feb 2018 12:14:51 +0100
> > Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > > This series adds support for a vgpu display to the qemu vfio code.
> > > For now only regions are supported, dmabufs will follow later.
> > >
> > > This version adds a patch to allow devices disable hotplugging, which
> > > will be used by vfio display support. Also fixed issues Alex found in
> > > review.
> >
> > Looks ok to me, if this is to go through my tree I'll need a qdev ack
> > for 4/7. If you want to go a different route, for 5-7:
> >
> > Acked-by: Alex Williamson <alex.williamson@redhat.com>
> >
> > I'm still a bit confused though, what's preventing us from adding
> > dmabuf support now? It's strange to provide the implementation for the
> > proprietary, unavailable vendor driver implementation first. Is GVT-g
> > broken, lagging? Thanks,
>
> A bit more complicated because it depends on user interface changes ...
>
> Sneak preview at https://www.kraxel.org/cgit/qemu/log/?h=work/intel-vgpu
> Note: branch is a moving target ;)
>
> State:
> vfio: Working, needs some cleanups though (drop debug logging, ...).
> gtk: Working, needs some minor cleanups too.
> spice: Partly working (no mouse ptr yet).
> sdl: Not working. Need to figure how I get a egl context (instead
> of glx). Possibly requires SDL 2.2. Tina looked at this a
> while back, need to look at some old mails ...
>
> Current plan:
> (1) fix/complete spice support.
> (2) cleanup patches, send them out.
> (3) look at the SDL issues.
Hi Gerd,
It's a little bit concerning that the only way we can test the
region-based display support is with proprietary drivers that nobody
but NVIDIA has at this point. Have you considered adding region-based
display support to the mdev sample tty driver? I know it sounds
ridiculous for a serial device to have a display, but the vfio display
region support isn't really tied to the functionality of the base mdev
device. We could have it simply display a static test pattern, just so
we can test the end to end code path without a dependency on a closed
vendor driver. Thanks,
Alex
next prev parent reply other threads:[~2018-02-22 16:28 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
2018-02-23 2:42 ` Zhenyu Wang
2018-02-23 7:06 ` Zhang, Tina
2018-02-22 16:28 ` Alex Williamson [this message]
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=20180222092811.0a705b9e@w520.home \
--to=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@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).