Linux IOMMU Development
 help / color / mirror / Atom feed
From: chenfeng <puck.chen@hisilicon.com>
To: joro@8bytes.org, iommu@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, rcallicotte@gmail.com,
	robin.murphy@arm.com, jiang.liu@linux.intel.com
Cc: Dan zhao <dan.zhao@hisilicon.com>,
	qijiwen <qijiwen@hisilicon.com>,
	Peter Panshilin <peter.panshilin@hisilicon.com>,
	Suzhuangluan <suzhuangluan@hisilicon.com>,
	Yiping Xu <xuyiping@hisilicon.com>,
	"Wangfei (William, Euler)" <w.f@huawei.com>
Subject: How to ensure that different peripherals getting different IOVA address in kernel?
Date: Wed, 23 Sep 2015 09:55:58 +0800	[thread overview]
Message-ID: <560206AE.4020608@hisilicon.com> (raw)
In-Reply-To: <5600AF72.2000106@hisilicon.com>

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

       reply	other threads:[~2015-09-23  1:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5600AF72.2000106@hisilicon.com>
2015-09-23  1:55 ` chenfeng [this message]
     [not found]   ` <560206AE.4020608-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2015-09-23  2:42     ` How to ensure that different peripherals getting different IOVA address in kernel? Jiang Liu
2015-09-23 12:08     ` Robin Murphy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560206AE.4020608@hisilicon.com \
    --to=puck.chen@hisilicon.com \
    --cc=dan.zhao@hisilicon.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jiang.liu@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.panshilin@hisilicon.com \
    --cc=qijiwen@hisilicon.com \
    --cc=rcallicotte@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=suzhuangluan@hisilicon.com \
    --cc=w.f@huawei.com \
    --cc=xuyiping@hisilicon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox