linux-kernel - Re: [Intel IOMMU 00/10] Intel IOMMU support, take #2

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: <46813E0F.1060806@linux.intel.com>
Date:	Tue, 26 Jun 2007 09:25:51 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Muli Ben-Yehuda <muli@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>,
	linux-kernel@...r.kernel.org, gregkh@...e.de,
	suresh.b.siddha@...el.com, ashok.raj@...el.com,
	davem@...emloft.net, clameter@....com
Subject: Re: [Intel IOMMU 00/10] Intel IOMMU support, take #2

Andi Kleen wrote:
> On Tue, Jun 26, 2007 at 08:15:05AM -0700, Arjan van de Ven wrote:
>>> Also the user interface for X server case needs more work.
>>>
>> actually with the mode setting of X moving into the kernel... X won't 
>> use /dev/mem anymore at all
> 
> We'll see if that happens. It has been talked about forever,
> but results are sparse. 

jbarnes posted the code a few weeks ago.

> 
>> (and I think it mostly already doesn't even without that)
> 
> It uses /sys/bus/pci/* which is not any better as seen from the IOMMU.
> 
> Any interface will need to be explicit because user space needs to know which
> DMA addresses to put into the hardware. It's not enough to just transparently
> translate the mappings.

that's what DRM is used for nowadays...
-
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/