Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Jerome Glisse <j.glisse-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: alexander.deucher-5C7GfCeVMHo@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: IOMMU and domain binding/unbinding logic
Date: Thu, 26 Mar 2015 18:09:35 +0100	[thread overview]
Message-ID: <20150326170935.GX4441@8bytes.org> (raw)
In-Reply-To: <20150326165046.GA2965-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Hi Jerome,

On Thu, Mar 26, 2015 at 12:50:47PM -0400, Jerome Glisse wrote:
> So how comes it still looks like it is working properly ? My best guest
> it is because it is by default in passthrough, but i haven't checked that
> theory.

Your guess is correct, devices that might potentially use IOMMUv2
functionality are identity mapped by default. The reason is that IOMMU
hardware implements two dimensional paging, where the addresses in the
guest page-tables (the ones translating PASID requests) are translated
by the host page-tables. So to be able to use CPU page-tables (mm->pgd)
for the IOMMU, the host page-tables need to be identity mapped.

The other reason is, as you observed already, that host-only dma
mappings need to work in parallel.


	Joerg

  parent reply	other threads:[~2015-03-26 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 16:50 IOMMU and domain binding/unbinding logic Jerome Glisse
     [not found] ` <20150326165046.GA2965-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-26 17:09   ` Joerg Roedel [this message]
     [not found]     ` <20150326170935.GX4441-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2015-03-26 17:58       ` Jerome Glisse
     [not found]         ` <20150326175857.GA3196-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-30  9:46           ` Joerg Roedel

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=20150326170935.GX4441@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=j.glisse-Re5JQEeQqe8AvxtiuMwx3w@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