linux-kernel - Re: [PATCH 07/19] OpenRISC: DMA

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]

Message-Id: <201106192102.30953.arnd@arndb.de>
Date:	Sun, 19 Jun 2011 21:02:30 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 07/19] OpenRISC: DMA

On Sunday 19 June 2011 13:43:33 Jonas Bonn wrote:
> 
> Simple DMA implementation.  There's some work to do here, but
> this allows for allocation of coherent memory (simply uncached) for DMA
> operations.
> 
> Signed-off-by: Jonas Bonn <jonas@...thpole.se>
> ---
>  arch/openrisc/include/asm/dma-mapping.h |  129 ++++++++++++++++++++++++++
>  arch/openrisc/kernel/dma.c              |  152 +++++++++++++++++++++++++++++++
>  2 files changed, 281 insertions(+), 0 deletions(-)
>  create mode 100644 arch/openrisc/include/asm/dma-mapping.h
>  create mode 100644 arch/openrisc/kernel/dma.c

If you don't have an IOMMU or the need for swiotlb, you can probably eliminate
the use of dma_map_ops and just provide the simple implementation.

For the operations that you have not implemented properly, I would leave
a forward-declaration but remove the implementation that causes a runtime
error, so you turn that into a link time error.

	Arnd
--
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/