All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: 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: Mon, 14 Nov 2016 20:05:16 -0500	[thread overview]
Message-ID: <20161115010516.GA3730@pxdev.xzpeter.org> (raw)
In-Reply-To: <1479171568-19175-1-git-send-email-peterx@redhat.com>

On Mon, Nov 14, 2016 at 07:59:28PM -0500, Peter Xu wrote:
> When one IOMMU memory region is splitted into multiple memory sections,
> vfio will register multiple same notifiers to a vIOMMU for the same
> region. That's not sensible. What we need is to register one IOMMU
> notifier for each IOMMU region, not per section.
> 
> Solution is simple - we traverse the container->giommu_list, and skip
> the registration if memory region is already registered.
> 
> To make vfio's region_add() short, vfio_listener_region_add_iommu() is
> introduced.
> 
> Signed-off-by: Peter Xu <peterx@redhat.com>

This patch will solve Aviv's issue that vfio_map_notify() will dump
many error messages when device assignments are enabled with Intel
vIOMMU.

Alex, could you help verify whether this is the one that you
suggested? I'd be glad to add your suggestted-by if you won't
disagree.

Thanks,

-- peterx

  reply	other threads:[~2016-11-15  1:05 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 [this message]
2016-11-15  5:11 ` Alexey Kardashevskiy
2016-11-15 15:49   ` Peter Xu
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=20161115010516.GA3730@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --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.