Displaying 9 results from an estimated 9 matches for "get_arch_dma_op".
Did you mean:
get_arch_dma_ops
2020 Feb 04
2
[PATCH 5/5] vdpasim: vDPA device simulator
...MHO, it would be nice if dma_ops of the parent device could be
> re-used. vdpa_device is expecting to represent a physical device
> except this simulator, however, there are not enough information in
> vdpa_device.dev to indicating which kind physical device it attached
> to. Namely get_arch_dma_ops(struct bus type) can not work on
> vdpa_device.dev. Then it seems device drivers need to implement a wrap
> of dma_ops of parent devices. Can this work be done in the vdpa
> framework since it looks like a common task? Can
> "vd_dev->vdev.dev.parent = vdpa->dev->paren...
2020 Feb 04
2
[PATCH 5/5] vdpasim: vDPA device simulator
...MHO, it would be nice if dma_ops of the parent device could be
> re-used. vdpa_device is expecting to represent a physical device
> except this simulator, however, there are not enough information in
> vdpa_device.dev to indicating which kind physical device it attached
> to. Namely get_arch_dma_ops(struct bus type) can not work on
> vdpa_device.dev. Then it seems device drivers need to implement a wrap
> of dma_ops of parent devices. Can this work be done in the vdpa
> framework since it looks like a common task? Can
> "vd_dev->vdev.dev.parent = vdpa->dev->paren...
2019 Oct 14
3
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
...f7..f92c0a4b 100644
> --- a/arch/powerpc/include/asm/dma-mapping.h
> +++ b/arch/powerpc/include/asm/dma-mapping.h
> @@ -5,6 +5,8 @@
> #ifndef _ASM_DMA_MAPPING_H
> #define _ASM_DMA_MAPPING_H
>
> +#include <asm/svm.h>
> +
> static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
> {
> /* We don't handle the NULL dev case for ISA for now. We could
> @@ -15,4 +17,23 @@ static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
> return NULL;
> }
>
> +#ifdef CONFIG_ARCH_HAS_DMA_ADDR_IS_PHYS_ADDR
>...
2019 Oct 14
3
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
...f7..f92c0a4b 100644
> --- a/arch/powerpc/include/asm/dma-mapping.h
> +++ b/arch/powerpc/include/asm/dma-mapping.h
> @@ -5,6 +5,8 @@
> #ifndef _ASM_DMA_MAPPING_H
> #define _ASM_DMA_MAPPING_H
>
> +#include <asm/svm.h>
> +
> static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
> {
> /* We don't handle the NULL dev case for ISA for now. We could
> @@ -15,4 +17,23 @@ static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
> return NULL;
> }
>
> +#ifdef CONFIG_ARCH_HAS_DMA_ADDR_IS_PHYS_ADDR
>...
2019 Oct 12
0
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
...powerpc/include/asm/dma-mapping.h
index 565d6f7..f92c0a4b 100644
--- a/arch/powerpc/include/asm/dma-mapping.h
+++ b/arch/powerpc/include/asm/dma-mapping.h
@@ -5,6 +5,8 @@
#ifndef _ASM_DMA_MAPPING_H
#define _ASM_DMA_MAPPING_H
+#include <asm/svm.h>
+
static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
{
/* We don't handle the NULL dev case for ISA for now. We could
@@ -15,4 +17,23 @@ static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
return NULL;
}
+#ifdef CONFIG_ARCH_HAS_DMA_ADDR_IS_PHYS_ADDR
+/**
+ * dma_addr_is_phys_addr - check w...
2019 Oct 14
0
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
...powerpc/include/asm/dma-mapping.h
>> +++ b/arch/powerpc/include/asm/dma-mapping.h
>> @@ -5,6 +5,8 @@
>> #ifndef _ASM_DMA_MAPPING_H
>> #define _ASM_DMA_MAPPING_H
>>
>> +#include <asm/svm.h>
>> +
>> static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
>> {
>> /* We don't handle the NULL dev case for ISA for now. We could
>> @@ -15,4 +17,23 @@ static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
>> return NULL;
>> }
>>
>> +#ifdef CONFIG_ARC...
2019 Oct 12
4
[PATCH 0/2] virtio: Support encrypted memory on powerpc secure guests
**We would like the patches to be merged through the virtio tree. Please
review, and ack merging the DMA mapping change through that tree. Thanks!**
The memory of powerpc secure guests can't be accessed by the hypervisor /
virtio device except for a few memory regions designated as 'shared'.
At the moment, Linux uses bounce-buffering to communicate with the
hypervisor, with a
2019 Apr 09
0
[RFC PATCH 03/12] s390/mm: force swiotlb for protected virtualization
> +++ b/arch/s390/include/asm/dma-mapping.h
> @@ -0,0 +1,13 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef _ASM_S390_DMA_MAPPING_H
> +#define _ASM_S390_DMA_MAPPING_H
> +
> +#include <linux/dma-contiguous.h>
> +
> +static inline const struct dma_map_ops *get_arch_dma_ops(struct bus_type *bus)
> +{
> + return NULL;
> +}
> +
> +#endif /* _ASM_S390_DMA_MAPPING_H */
> +
Congratulations! You ust create an entirely pointless duplicate of
include/asm-generic/dma-mapping.h.
2020 Feb 04
0
[PATCH 5/5] vdpasim: vDPA device simulator
...nice if dma_ops of the parent device could be re-used.
> > vdpa_device is expecting to represent a physical device except this
> > simulator, however, there are not enough information in vdpa_device.dev
> > to indicating which kind physical device it attached to. Namely
> > get_arch_dma_ops(struct bus type) can not work on vdpa_device.dev. Then
> > it seems device drivers need to implement a wrap of dma_ops of parent
> > devices. Can this work be done in the vdpa framework since it looks like
> > a common task? Can "vd_dev->vdev.dev.parent = vdpa->dev->...