From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"kwankhede@nvidia.com" <kwankhede@nvidia.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: [PATCH v16 5/6] vfio: ABI for mdev display dma-buf operation
Date: Wed, 08 Nov 2017 09:25:49 +0100 [thread overview]
Message-ID: <1510129549.23170.1.camel@redhat.com> (raw)
In-Reply-To: <20171107094829.1d7589eb@t450s.home>
Hi,
> Should we then specify the error code for "head doesn't exist" vs
> "head
> doesn't support dmabuf", with the former taking precedence? Perhaps
> -ENODEV vs -EINVAL.
NODEV for "head doesn't exist" and INVAL for "head doesn't support
dmabuf/region/..." ?
> Are the heads guaranteed to be contiguous (the
> first -ENODEV is the end of possible heads)?
Yes, I think the valid heads should be contignous. The guest might
still only use a non-contignous subset of the available heads though.
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-08 8:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 2:19 [PATCH v16 0/6] drm/i915/gvt: Dma-buf support for GVT-g Tina Zhang
2017-11-06 2:19 ` [PATCH v16 1/6] drm/i915/gvt: Add framebuffer decoder support Tina Zhang
2017-11-06 8:48 ` Gerd Hoffmann
2017-11-06 9:07 ` Zhang, Tina
2017-11-06 2:19 ` [PATCH v16 2/6] drm: Introduce RGB 64-bit 16:16:16:16 float format Tina Zhang
2017-11-06 2:19 ` [PATCH v16 3/6] drm/i915/gvt: Add " Tina Zhang
2017-11-06 2:19 ` [PATCH v16 4/6] drm/i915/gvt: Add opregion support Tina Zhang
2017-11-06 2:19 ` [PATCH v16 5/6] vfio: ABI for mdev display dma-buf operation Tina Zhang
2017-11-06 2:39 ` Alex Williamson
2017-11-06 6:58 ` Zhang, Tina
2017-11-06 9:05 ` Gerd Hoffmann
2017-11-06 20:36 ` Alex Williamson
2017-11-07 5:00 ` Zhang, Tina
2017-11-06 9:01 ` Gerd Hoffmann
2017-11-07 5:44 ` Zhang, Tina
2017-11-07 8:03 ` Gerd Hoffmann
2017-11-07 16:48 ` Alex Williamson
2017-11-08 8:25 ` Gerd Hoffmann [this message]
2017-11-08 21:19 ` Alex Williamson
2017-11-08 5:21 ` Zhang, Tina
2017-11-06 2:19 ` [PATCH v16 6/6] drm/i915/gvt: Dmabuf support for GVT-g Tina Zhang
2017-11-06 2:26 ` ✗ Fi.CI.BAT: failure for drm/i915/gvt: Dma-buf " Patchwork
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=1510129549.23170.1.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kwankhede@nvidia.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).