linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <560206AE.4020608@hisilicon.com>
Date:	Wed, 23 Sep 2015 09:55:58 +0800
From:	chenfeng <puck.chen@...ilicon.com>
To:	<joro@...tes.org>, <iommu@...ts.linux-foundation.org>,
	<linux-kernel@...r.kernel.org>, <rcallicotte@...il.com>,
	<robin.murphy@....com>, <jiang.liu@...ux.intel.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: How to ensure that different peripherals getting different IOVA
 address in kernel?

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.

Puck

--
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/