Displaying 4 results from an estimated 4 matches for "932d6562179e".
2019 Nov 01
1
[PATCH v2 08/15] xen/gntdev: Use select for DMA_SHARED_BUFFER
...(it represents a library
> set in the kernel). The kconfig convention is to use select for such
> symbols so they are turned on implicitly when the user enables a kconfig
> that needs them.
>
> Otherwise the XEN_GNTDEV_DMABUF kconfig is overly difficult to enable.
>
> Fixes: 932d6562179e ("xen/gntdev: Add initial support for dma-buf UAPI")
> Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko at epam.com>
> Cc: Boris Ostrovsky <boris.ostrovsky at oracle.com>
> Cc: xen-devel at lists.xenproject.org
> Cc: Juergen Gross <jgross at suse.com>
>...
2019 Nov 05
0
[PATCH v2 08/15] xen/gntdev: Use select for DMA_SHARED_BUFFER
...>> set in the kernel). The kconfig convention is to use select for such
>> symbols so they are turned on implicitly when the user enables a kconfig
>> that needs them.
>>
>> Otherwise the XEN_GNTDEV_DMABUF kconfig is overly difficult to enable.
>>
>> Fixes: 932d6562179e ("xen/gntdev: Add initial support for dma-buf UAPI")
>> Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko at epam.com>
>> Cc: Boris Ostrovsky <boris.ostrovsky at oracle.com>
>> Cc: xen-devel at lists.xenproject.org
>> Cc: Juergen Gross <jgross at...
2019 Oct 28
0
[PATCH v2 08/15] xen/gntdev: Use select for DMA_SHARED_BUFFER
...FFER can not be enabled by the user (it represents a library
set in the kernel). The kconfig convention is to use select for such
symbols so they are turned on implicitly when the user enables a kconfig
that needs them.
Otherwise the XEN_GNTDEV_DMABUF kconfig is overly difficult to enable.
Fixes: 932d6562179e ("xen/gntdev: Add initial support for dma-buf UAPI")
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko at epam.com>
Cc: Boris Ostrovsky <boris.ostrovsky at oracle.com>
Cc: xen-devel at lists.xenproject.org
Cc: Juergen Gross <jgross at suse.com>
Cc: Stefano Stabellini...
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others