linux-kernel - Re: [PATCH 0 of 9] swiotlb: use phys_addr

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:	Sun, 28 Dec 2008 10:37:51 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	jeremy@...p.org, tony.luck@...el.com, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com, x86@...nel.org,
	ian.campbell@...rix.com, beckyb@...nel.crashing.org,
	Joerg Roedel <joerg.roedel@....com>
Subject: Re: [PATCH 0 of 9] swiotlb: use phys_addr_t for pages

* FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:

> If we really want to clean up the dma mapping operations, we should 
> define struct dma_mapping_ops in a generic place (such as 
> include/linux/dma-mapping.h) instead each architecture define the own 
> struct dma_mapping_ops. These dma_mapping_ops structures are very 
> similar but a bit different. That's the root cause of the dma mapping 
> operation ugliness.
>
> If we do, X86 and IA64 can share swiotlb and intel VTD code cleanly, 
> X86, IA64, and POWERPC can share swiotlb cleanly too. For example, we 
> can define swiotlb_dma_ops in lib/swiotlb.c and then everyone can share 
> it. Currently, X86 and IA64 define the own swiotlb_dma_ops (and X86 
> needs swiotlb_map_single_phys hack). It doesn't make sense.

Sure.

Note that we went through this process (of unifying dma_mapping_ops) 
recently on x86 recently - 32-bit and 64-bit x86 had such differences.

Note that the main complication wasnt even the small variations in 
signatures, but the different _semantics_: one dma_mapping_ops 
implementation passed in kernel-virtual addresses, the other physical 
addresses. Unifying that was invasive and non-trivial, and it can break 
stuff not at the build level but at the runtime level. We can expect 
similar complications when done over 20 architectures as well.

But yes, it's all desired. Obviously extending swiotlb to highmem and 
using it on xen and powerpc is an essential first step in the direction of 
generalizing all this code.

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