Am 18.04.19 um 11:13 schrieb Daniel Vetter:
On Tue, Apr 16, 2019 at 08:38:29PM +0200, Christian König wrote:
Hi everybody,
core idea in this patch set is that DMA-buf importers can now provide an
optional invalidate callback. Using this callback and the reservation object
exporters can now
On Tue, Apr 16, 2019 at 08:38:29PM +0200, Christian König wrote:
> Hi everybody,
>
> core idea in this patch set is that DMA-buf importers can now provide an
> optional invalidate callback. Using this callback and the reservation object
> exporters can now avoid pinning DMA-buf memory for a
I like you do somethings step by step, you can ping me when they are ready.
-David
在 2019/4/17 21:59, Christian König 写道:
> On top of those I have 6 more patches in the pipeline to enable VRAM
> P2P with DMA-buf.
>
> So that is not the end of the patch set :)
>
> Christian.
>
> Am 17.04.19 um
On top of those I have 6 more patches in the pipeline to enable VRAM P2P
with DMA-buf.
So that is not the end of the patch set :)
Christian.
Am 17.04.19 um 15:52 schrieb Chunming Zhou:
Thanks Christian, great job. I will verify it this week when I finish my
current work on hand.
-David
在
Thanks Christian, great job. I will verify it this week when I finish my
current work on hand.
-David
在 2019/4/17 2:38, Christian König wrote:
> Hi everybody,
>
> core idea in this patch set is that DMA-buf importers can now provide an
> optional invalidate callback. Using this callback and
Hi everybody,
core idea in this patch set is that DMA-buf importers can now provide an
optional invalidate callback. Using this callback and the reservation object
exporters can now avoid pinning DMA-buf memory for a long time while sharing it
between devices.
I've already send out an older