linux-kernel - Re: How to ensure that different peripherals getting different IOVA address in kernel?

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]

Message-ID: <56021186.4010500@linux.intel.com>
Date:	Wed, 23 Sep 2015 10:42:14 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	chenfeng <puck.chen@...ilicon.com>, joro@...tes.org,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	rcallicotte@...il.com, robin.murphy@....com
Cc:	Dan zhao <dan.zhao@...ilicon.com>, qijiwen <qijiwen@...ilicon.com>,
	Peter Panshilin <peter.panshilin@...ilicon.com>,
	Suzhuangluan <suzhuangluan@...ilicon.com>,
	Yiping Xu <xuyiping@...ilicon.com>,
	"Wangfei (William, Euler)" <w.f@...wei.com>
Subject: Re: How to ensure that different peripherals getting different IOVA
 address in kernel?

On 2015/9/23 9:55, chenfeng wrote:
> Hi all,
> 
> In IOMMU architecture , how to make two different peripherals share the same page table ?
> 
> In other words , is there a mechanism or structure to make two peripherals get completely different address.
> 
> eg:
> 
> peri-A、peri-B and peri-C share the same iova address 0-1G for some performance requests.
> 
> So the A,B,C need to use the same IOVA generator to ensure this,but I don't find an architecture to make this.
> 
> Any help will be appreciated.
Hi Chenfeng,
	Seems IOMMU group may help you, please take a look at
Documentation/vfio.txt.
Thanks!
Gerry
--
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/