qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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>,
	Laine Stump <laine@redhat.com>,
	Erik Skultety <eskultet@redhat.com>,
	libvir-list@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/7] vfio: add display support
Date: Tue, 27 Feb 2018 11:32:51 -0700	[thread overview]
Message-ID: <20180227113251.3d24a58f@w520.home> (raw)
In-Reply-To: <20180227085209.19151-1-kraxel@redhat.com>

[CC +libvirt]

On Tue, 27 Feb 2018 09:52:02 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:

> This series adds support for a vgpu display to the qemu vfio code.
> 
> v5:
>  - rebase to latest master
>  - drop DeviceState->hotpluggable patch, use separate vfio-pci-display
>    device instead so we can use DeviceClass->hotpluggable.

I can't imagine that management layers are going to be happy with this
approach, it's one thing to have certain USB controllers where the
version intimately tied to the machine chipset is not hotpluggable,
while standalone versions are, but having a fork of an entirely
standalone device for this purpose sounds very invasive.  What does the
XML look like that would make libvirt select this option?  I'm still
thinking that a separate display device, which vfio-pci can bind to as
a device option, not affecting the hotplug-ability of the vfio-pci
device itself is the correct, but clearly difficult, approach to this.
I can't agree to a separate device unless libvirt is willing to sign up
for enabling it.

Furthermore, if we take the separate device approach, shouldn't it be
something like vfio-pci-nohotplug, where display is an option only for
this version of the DeviceClass?  Thanks,

Alex

>  - add vfio dma-buf patch.  Right now this can be tested with '-display
>    egl-headless' only.  gtk and spice support is almost ready for merge
>    and should follow soon.
> 
> cheers,
>   Gerd
> 
> Gerd Hoffmann (7):
>   linux-headers: update to 4.16-rc1
>   standard-headers: add drm/drm_fourcc.h
>   ui/pixman: add qemu_drm_format_to_pixman()
>   vfio/common: cleanup in vfio_region_finalize
>   vfio/display: core & wireup
>   vfio/display: adding region support
>   vfio/display: adding dmabuf support
> 
>  hw/vfio/pci.h                                      |   4 +
>  include/hw/vfio/vfio-common.h                      |  22 ++
>  include/standard-headers/drm/drm_fourcc.h          | 411 +++++++++++++++++++++
>  include/standard-headers/linux/input-event-codes.h |   1 +
>  include/standard-headers/linux/input.h             |  11 +
>  include/standard-headers/linux/pci_regs.h          |  30 +-
>  include/standard-headers/linux/virtio_net.h        |  13 +
>  include/ui/qemu-pixman.h                           |   5 +
>  linux-headers/asm-powerpc/kvm.h                    |   2 +
>  linux-headers/asm-powerpc/unistd.h                 |   3 +
>  linux-headers/asm-s390/unistd.h                    | 401 +-------------------
>  linux-headers/asm-s390/unistd_32.h                 | 364 ++++++++++++++++++
>  linux-headers/asm-s390/unistd_64.h                 | 331 +++++++++++++++++
>  linux-headers/asm-x86/kvm_para.h                   |   4 +
>  linux-headers/linux/kvm.h                          |  90 +++++
>  linux-headers/linux/psci.h                         |   3 +
>  linux-headers/linux/vfio.h                         |  72 ++++
>  hw/vfio/common.c                                   |   7 +
>  hw/vfio/display.c                                  | 286 ++++++++++++++
>  hw/vfio/pci.c                                      |  30 ++
>  ui/qemu-pixman.c                                   |  22 ++
>  hw/vfio/Makefile.objs                              |   2 +-
>  scripts/update-linux-headers.sh                    |   7 +
>  23 files changed, 1710 insertions(+), 411 deletions(-)
>  create mode 100644 include/standard-headers/drm/drm_fourcc.h
>  create mode 100644 linux-headers/asm-s390/unistd_32.h
>  create mode 100644 linux-headers/asm-s390/unistd_64.h
>  create mode 100644 hw/vfio/display.c
> 

      parent reply	other threads:[~2018-02-27 18:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27  8:52 [Qemu-devel] [PATCH v5 0/7] vfio: add display support Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 1/7] linux-headers: update to 4.16-rc1 Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 2/7] standard-headers: add drm/drm_fourcc.h Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 3/7] ui/pixman: add qemu_drm_format_to_pixman() Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 4/7] vfio/common: cleanup in vfio_region_finalize Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 5/7] vfio/display: core & wireup Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 6/7] vfio/display: adding region support Gerd Hoffmann
2018-02-27  8:52 ` [Qemu-devel] [PATCH v5 7/7] vfio/display: adding dmabuf support Gerd Hoffmann
2018-02-27 18:32 ` Alex Williamson [this message]

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=20180227113251.3d24a58f@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=eskultet@redhat.com \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=kwankhede@nvidia.com \
    --cc=laine@redhat.com \
    --cc=libvir-list@redhat.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).