Linux IOMMU Development
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: chenfeng <puck.chen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
	"joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org"
	<joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>,
	"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"rcallicotte-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
	<rcallicotte-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
	<jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Dan zhao <dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
	"Wangfei (William,
	Euler)" <w.f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Suzhuangluan
	<suzhuangluan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
	qijiwen <qijiwen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>,
	Peter Panshilin
	<peter.panshilin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
Subject: Re: How to ensure that different peripherals getting different IOVA address in kernel?
Date: Wed, 23 Sep 2015 13:08:28 +0100	[thread overview]
Message-ID: <5602963C.8030601@arm.com> (raw)
In-Reply-To: <560206AE.4020608-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>

On 23/09/15 02: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.

This is what IOMMU domains are all about: devices in one domain are 
isolated from devices in different domains, so all you need to do is 
make sure all devices that want to share buffers are attached to the 
same domain, then they will all share that domain's IOVA space.

Robin.

>
> Any help will be appreciated.
>
> Puck
>
>

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

      parent reply	other threads:[~2015-09-23 12:08 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 ` How to ensure that different peripherals getting different IOVA address in kernel? chenfeng
     [not found]   ` <560206AE.4020608-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2015-09-23  2:42     ` Jiang Liu
2015-09-23 12:08     ` Robin Murphy [this message]

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=5602963C.8030601@arm.com \
    --to=robin.murphy-5wv7dgnigg8@public.gmane.org \
    --cc=dan.zhao-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=peter.panshilin-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    --cc=puck.chen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    --cc=qijiwen-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    --cc=rcallicotte-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=suzhuangluan-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org \
    --cc=w.f-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    /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