linux-kernel - Re: [Intel IOMMU][patch 8/8] Preserve some Virtual Address when devices cannot address entire range.

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: <20070424.144733.10245273.davem@davemloft.net>
Date:	Tue, 24 Apr 2007 14:47:33 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rdreier@...co.com
Cc:	ak@...e.de, ashok.raj@...el.com, linux-kernel@...r.kernel.org,
	akpm@...l.org, gregkh@...e.de, muli@...ibm.com,
	asit.k.mallick@...el.com, suresh.b.siddha@...el.com,
	anil.s.keshavamurthy@...el.com, arjan@...ux.intel.com,
	shaohua.li@...el.com
Subject: Re: [Intel IOMMU][patch 8/8] Preserve some Virtual Address when
 devices cannot address entire range.

From: Roland Dreier <rdreier@...co.com>
Date: Tue, 24 Apr 2007 14:32:42 -0700

>  > My suggestion would be to allocate top-down in the 32-bit IOMMU space.
> 
> I think that's good for normal things, but it's not unreasonable to
> want to map > 4 GB of memory at once for an Infiniband device.

That's what the DAC interfaces were for, but people wanted to
remoe that since no in-tree users existed.

Devices like that want to essentially map the entire address space,
via pass-thru, not IOMMU mappings.

Clustering cards, such as those made by Dolphin, are another example.

I realize that this doesn't work when we absolutely must use an IOMMU
such as for virtualization which is the whole impetus of the Intel
IOMMU. :-)

> So maybe we would want some heuristics about the size of the mapping
> being requested or the amount of 32-bit space left to decide whether a
> mapping should be below 4 GB.

Perhaps, but as I said heuristics might not be enough here.
-
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/