linux-kernel - Re: [patch 5/8] [Intel IOMMU] Graphics driver workarounds to provide unity map

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Apr 2007 09:29:26 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	David Miller <davem@...emloft.net>
CC:	hch@...radead.org, ashok.raj@...el.com,
	linux-kernel@...r.kernel.org, akpm@...l.org, ak@...e.de,
	gregkh@...e.de, muli@...ibm.com, asit.k.mallick@...el.com,
	suresh.b.siddha@...el.com, anil.s.keshavamurthy@...el.com,
	shaohua.li@...el.com
Subject: Re: [patch 5/8] [Intel IOMMU] Graphics driver workarounds to provide
 unity map

David Miller wrote:
> From: Christoph Hellwig <hch@...radead.org>
> Date: Tue, 10 Apr 2007 09:33:51 +0100
> 
>> On Mon, Apr 09, 2007 at 02:55:57PM -0700, Ashok Raj wrote:
>>> Most GFX drivers don't call standard PCI DMA APIs to allocate DMA buffer,
>>> Such drivers will be broken with IOMMU enabled. To workaround this issue, 
>>> we added two options.
>> All drm drivers do it.  If the usual out of tree crap vendors are too
>> stupid for their own sake it's their fault.
>>
>> So NACK to this patch.
> 
> That's my feeling as well, everything we care about should be using
> the proper APIs or else what is the point of them...

that's too simple; X uses /dev/mem as well, even with something as 
open as the Intel drivers.

Sad but true ;(

(it's getting resolved on the X side but existing X is like this)
-
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/