linux-kernel - Re: [RFC PATCH 1/3] dma-fence: dma-buf synchronization (v5)

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 6 Aug 2012 12:11:25 +0530
From:	Sumit Semwal <sumit.semwal@...aro.org>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Cc:	linaro-mm-sig@...ts.linaro.org, rob.clark@...aro.org,
	dri-devel@...ts.freedesktop.org, linux-media@...r.kernel.org,
	patches@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/3] dma-fence: dma-buf synchronization (v5)

Hi Maarten,
On 27 July 2012 19:09, Maarten Lankhorst
<maarten.lankhorst@...onical.com> wrote:
> A dma-fence can be attached to a buffer which is being filled or consumed
> by hw, to allow userspace to pass the buffer without waiting to another
> device.  For example, userspace can call page_flip ioctl to display the
> next frame of graphics after kicking the GPU but while the GPU is still
> rendering.  The display device sharing the buffer with the GPU would
> attach a callback to get notified when the GPU's rendering-complete IRQ
> fires, to update the scan-out address of the display, without having to
> wake up userspace.
Since Rob is the original author of this (and I the next?), may I
request you to re-submit with his "From:" bit?

Rob / Daniel: comments on this series will help me line it up in
for-next, and maybe even for 3.7-rc.

Best regards,
~Sumit.
<snip>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/