linux-kernel - Re: [PATCH] x86 DMA: Handle devices assigned to the guest by the host

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: <20080430062940.GM7378@il.ibm.com>
Date:	Wed, 30 Apr 2008 09:29:41 +0300
From:	Muli Ben-Yehuda <muli@...ibm.com>
To:	Amit Shah <amit.shah@...ranet.com>
Cc:	kvm-devel@...ts.sourceforge.net,
	virtualization@...ts.linux-foundation.org,
	Ben-Ami Yassour1 <BENAMI@...ibm.com>, gcosta@...hat.com,
	chrisw@...hat.com, dor.laor@...ranet.com, allen.m.kay@...el.com,
	avi@...ranet.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86 DMA: Handle devices assigned to the guest by the
	host

On Tue, Apr 29, 2008 at 01:37:29PM +0300, Amit Shah wrote:

> dma_alloc_coherent() doesn't call dma_ops->alloc_coherent in case no
> IOMMU translations are necessary.

I always thought this was a huge wart in the x86-64 DMA ops. Would
there be strong resistance to fixing it so that alloc_coherent
matches the way the other ops are used? This will eliminate the need
for this patch and will make other DMA ops implementations saner.

Cheers,
Muli
--
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/