Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1645306
| From | Gerd Hoffmann <kraxel@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf |
| Date | 2017-05-19 10:10 +0200 |
| Message-ID | <tIL8Z-7Kt-1@gated-at.bofh.it> (permalink) |
| References | (14 earlier) <tHsi7-2M0-23@gated-at.bofh.it> <tHHKa-4hW-15@gated-at.bofh.it> <tIeZs-8x-27@gated-at.bofh.it> <tIiTn-2In-7@gated-at.bofh.it> <tIv4d-47X-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi, > > User space need to check whether there's a dmabuf for the plane(user space usually cached two or three dmabuf to handle double buffer or triple buffer situation) only there's no dmabuf for the plane we will create a dmabuf for it(another ioctl). > > If our ioctls are "Query current plane" and "Give me a dmabuf for > current plane", isn't that racey? The current plane could have changed > between those two calls so the user doesn't absolutely know which plane > the dmabuf retrieved is for. The "Give me a dmabuf" therefore needs to > take some sort of plane index so the user can request a specific > plane. The "give me a dmabuf" ioctl returns the plane description too, so userspace can at least figure it did hit the race window. We could also do it the other way around: Instead of having the kernel returning the plane description userspace could pass it in, and the kernel throws -EINVAL in case it doesn't match due to things having changed meanwhile. cheers, Gerd
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-12 04:20 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Alex Williamson <alex.williamson@redhat.com> - 2017-05-12 05:00 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-12 06:00 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Gerd Hoffmann <kraxel@redhat.com> - 2017-05-12 11:20 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Alex Williamson <alex.williamson@redhat.com> - 2017-05-12 18:50 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-15 05:40 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Alex Williamson <alex.williamson@redhat.com> - 2017-05-15 19:50 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-16 12:20 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Alex Williamson <alex.williamson@redhat.com> - 2017-05-17 23:50 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-18 04:00 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Alex Williamson <alex.williamson@redhat.com> - 2017-05-18 17:00 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-19 08:30 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Gerd Hoffmann <kraxel@redhat.com> - 2017-05-19 10:10 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-19 10:20 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Gerd Hoffmann <kraxel@redhat.com> - 2017-05-19 11:00 +0200
RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf "Chen, Xiaoguang" <xiaoguang.chen@intel.com> - 2017-05-19 11:20 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Gerd Hoffmann <kraxel@redhat.com> - 2017-05-19 13:00 +0200
Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf Gerd Hoffmann <kraxel@redhat.com> - 2017-05-18 08:30 +0200
csiph-web