lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 12 May 2017 06:56:03 +0000
From:   "Chen, Xiaoguang" <>
To:     Gerd Hoffmann <>
CC:     "Tian, Kevin" <>,
        "" <>,
        "" <>,
        "" <>,
        Alex Williamson <>,
        "Lv, Zhiyuan" <>,
        "Wang, Zhi A" <>
Subject: RE: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

Hi Gerd,

>-----Original Message-----
>From: intel-gvt-dev [] On
>Behalf Of Gerd Hoffmann
>Sent: Thursday, May 11, 2017 9:28 PM
>To: Chen, Xiaoguang <>
>Cc: Tian, Kevin <>;; linux-
>;; Alex Williamson
><>; Lv, Zhiyuan <>; intel-gvt-
>; Wang, Zhi A <>
>Subject: Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf
>  Hi,
>> While read the framebuffer region we have to tell the vendor driver which
>framebuffer we want to read? There are two framebuffers now in KVMGT that is
>primary and cursor.
>> There are two methods to implement this:
>> 1) write the plane id first and then read the framebuffer.
>> 2) create 2 vfio regions one for primary and one for cursor.
>(3) Place information for both planes into one vfio region.
>    Which allows to fetch both with a single read() syscall.
That works too. Then using the ioctl to get the dmabuf fd if needed. And plane id can be ioctl's parameter.

How about method 2 primary plane and cursor plane are different and should generate different dmabuf for each of them.

>The question is how you'll get the file descriptor then.  If the ioctl returns the
>dma-buf fd only you have a racy interface:  Things can change between read(vfio-
>region) and ioctl(need-dmabuf-fd).
You are right. So when creating the dmabuf we may have to decode the framebuffer and create the dmabuf using the latest framebuffer information and we must return the framebuffer information together with the dmabuf fd.

In the current implementation I saved the framebuffer information while user querying the framebuffer and generate the dmabuf using the saved information no error found yet but in theory there are sync problems.

>ioctl(need-dma-buf) could return both dmabuf fd and plane info to fix the race,
>but then it is easier to go with ioctl only interface (simliar to the orginal one from
>dec last year) I think.
Yes. ioctl works for it.
But based on the mail last week. If I understand correctly Alex hope to query the framebuffer information by reading the vfio device region and then get the dmabuf fd using ioctl.

>  Gerd
>intel-gvt-dev mailing list

Powered by blists - more mailing lists