All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, alex.williamson@redhat.com,
	bd.aviv@gmail.com, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH] vfio: avoid adding same iommu mr for notify
Date: Tue, 15 Nov 2016 10:49:38 -0500	[thread overview]
Message-ID: <20161115154710.GA19487@pxdev.xzpeter.org> (raw)
In-Reply-To: <3d39c9f6-6adc-bfef-b3c6-d30f4b93b06c@ozlabs.ru>

On Tue, Nov 15, 2016 at 04:11:57PM +1100, Alexey Kardashevskiy wrote:
> On 15/11/16 11:59, Peter Xu wrote:
> > When one IOMMU memory region is splitted into multiple memory sections,
> 
> 
> Out of curiosity - when does this happen?

My understanding: each PCI device will have one IOMMU region when with
vt-d vIOMMU enabled. After interrupt remapping is enabled, another
0xfeexxxxx region is overlapped to filter out the interrupts (see
vtd_find_add_as()). So the big Intel IOMMU region is splitted into
several.

Of course looks like we can remove the interrupt region and only use
one IOMMU region for both DMAR and IR, but I don't think that's a good
one, since maybe one day we'll have another scenario that will split a
single memory region. In that case, I'd prefer we take care of it
during registration.

Thanks,

-- peterx

  reply	other threads:[~2016-11-15 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  0:59 [Qemu-devel] [PATCH] vfio: avoid adding same iommu mr for notify Peter Xu
2016-11-15  1:05 ` Peter Xu
2016-11-15  5:11 ` Alexey Kardashevskiy
2016-11-15 15:49   ` Peter Xu [this message]
2016-11-17  3:24 ` David Gibson
2016-11-21  6:06   ` Peter Xu

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=20161115154710.GA19487@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=bd.aviv@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.