linux-kernel - Re: [kraxel@...hat.com: Re: [Intel-gfx] [PATCH v9 5/7] vfio: Define vfio based dma-buf operations]

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <594CE0AF.9070402@intel.com>
Date:   Fri, 23 Jun 2017 17:34:39 +0800
From:   Zhi Wang <zhi.a.wang@...el.com>
To:     Gerd Hoffmann <kraxel@...hat.com>
CC:     Alex Williamson <alex.williamson@...hat.com>,
        "Wang, Zhenyu Z" <zhenyu.z.wang@...el.com>,
        intel-gfx@...ts.freedesktop.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Zhang, Tina" <tina.zhang@...el.com>, kwankhede@...dia.com,
        Zhiyuan Lv <zhiyuan.lv@...el.com>,
        "intel-gvt-dev@...ts.freedesktop.org" 
        <intel-gvt-dev@...ts.freedesktop.org>
Subject: Re: [kraxel@...hat.com: Re: [Intel-gfx] [PATCH v9 5/7] vfio: Define
 vfio based dma-buf operations]

Hi Gred and Alex:
     Thanks for the reply! It would be better that kernel only provides 
functions instead of maintaining states from my point of view. If there 
is any existing async notification channel in vfio device fd? like 
reporting device events from vfio to QEMU? If so, It would be nice if we 
can extend that channel and notify the userspace application that guest 
framebuffer changed via that channel. So userspace application even 
doesn't need to call the ioctl periodically. :) If VM runs a 
single-buffered application.

Thanks,
Zhi.

On Fri, 2017-06-23 at 15:49 +0800, Zhi Wang wrote:
>> Hi:
>>       Thanks for the discussions! If the userspace application has
>> already maintained a LRU list, it looks like we don't need
>> generation
>> anymore,
> generation isn't required, things are working just fine without that.
> It is just a small optimization, userspace can skip the LRU lookup
> altogether if the generation didn't change.
>
> But of couse that only pays off if the kernel doesn't has to put much
> effort into maintaining the generation id.  Something simple like
> increasing it each time the guest writes a register which affects
> plane_info.
>
> If you think it doesn't make sense from the driver point of view we can
> drop the generation.
>
> cheers,
>    Gerd