linux-kernel - Re: [RFC] ARM DMA mapping TODO, v1

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:	Thu, 28 Apr 2011 14:15:51 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Joerg Roedel <joro@...tes.org>,
	Marek Szyprowski <m.szyprowski@...sung.com>
Cc:	linaro-mm-sig@...ts.linaro.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] ARM DMA mapping TODO, v1

On Thursday 28 April 2011, Joerg Roedel wrote:
> On Thu, Apr 21, 2011 at 09:29:16PM +0200, Arnd Bergmann wrote:
> > 4. Implement an architecture independent version of dma_map_ops
> >    based on the iommu.h API. As Joerg mentioned, this has been
> >    missing for some time, and it would be better to do it once
> >    than for each IOMMU separately. This is probably a lot of work.
> 
> Yes, thats missing for a long time. It will also need some changes to
> the IOMMU-API but that should be doable. The best would be to extend the
> IOMMU-API so that it also supports GART-like IOMMUs. This way every
> dma_ops implementation on all the architectures providing such an IOMMU
> could be covered with the architecture independent dma_ops
> implementation. This would only leave the low-level hardware access in
> the IOMMU drivers.
> I think this also requires to change the current semantics of the
> existing IOMMU-API implementations. I will prepare a write-up of my
> ideas for discussion.

Ok, thanks!

Please include Marek in this, he said he has already started with an
implementation. Any insight from you will certainly help.

	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/