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]

Message-Id: <20081228183054Y.fujita.tomonori@lab.ntt.co.jp>
Date:	Sun, 28 Dec 2008 18:36:07 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	hch@...radead.org
Cc:	fujita.tomonori@....ntt.co.jp, mingo@...e.hu, 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
Subject: Re: [PATCH 0 of 9] swiotlb: use phys_addr_t for pages

On Sun, 28 Dec 2008 02:30:12 -0500
Christoph Hellwig <hch@...radead.org> wrote:

> On Sun, Dec 28, 2008 at 02:29:54PM +0900, FUJITA Tomonori 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.
> 
> Yes, please.  For people hacking on different architectures occasionally
> the current setup with per-arch ops (and sometimes none at all) is pain.

The biggest obstacle is IA64's way to handle multiple dma mapping
operations (artistic define magics).

I'll take care of the cleanups if Tony lets me change IA64 to handle
multiple dma mapping operations as other architectures do (x86 and
powerpc).
--
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/