linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@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,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v17 5/6] vfio: ABI for mdev display dma-buf operation
Date: Thu, 9 Nov 2017 19:35:14 +0100	[thread overview]
Message-ID: <20171109183514.w3tbqumovglr4sri@sirius.home.kraxel.org> (raw)
In-Reply-To: <20171109082956.2c490080@t450s.home>

  Hi,

> struct vfio_device_gfx_plane_info lacks the head field we've been
> discussing.  Thanks,

Adding multihead support turned out to not be that easy.  There are
corner cases like a single framebuffer spawning both heads.  Also it
would be useful to somehow hint to the guest which heads it should use.

In short:  Proper multihead support is more complex than just adding a
head field for later use.  So in a short private discussion with Tina we
came to the conclusion that it will be better add multihead support to
the API when the first driver wants use it, so we can actually test the
interface and make sure we didn't miss anything.  Adding a incomplete
multihead API now doesn't help anybody.

cheers,
  Gerd

  reply	other threads:[~2017-11-09 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09  9:33 [PATCH v17 0/6] drm/i915/gvt: Dma-buf support for GVT-g Tina Zhang
2017-11-09  9:33 ` [PATCH v17 1/6] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-11-09  9:33 ` [PATCH v17 2/6] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-11-09  9:33 ` [PATCH v17 3/6] drm/i915/gvt: Add " Tina Zhang
2017-11-09  9:34 ` [PATCH v17 4/6] drm/i915/gvt: Add opregion support Tina Zhang
2017-11-09  9:34 ` [PATCH v17 5/6] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-11-09 15:29   ` Alex Williamson
2017-11-09 18:35     ` Gerd Hoffmann [this message]
2017-11-09 20:54       ` Alex Williamson
2017-11-10  7:02         ` Gerd Hoffmann
2017-11-11  2:04           ` Zhang, Tina
2017-11-09  9:34 ` [PATCH v17 6/6] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-11-09 14:09 ` [PATCH v17 0/6] drm/i915/gvt: Dma-buf " Gerd Hoffmann
2017-11-09 23:19   ` Zhang, Tina
2017-11-09 23:27   ` 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=20171109183514.w3tbqumovglr4sri@sirius.home.kraxel.org \
    --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=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=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;
as well as URLs for NNTP newsgroup(s).