All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgibson@redhat.com, jasowang@redhat.com, mst@redhat.com,
	pbonzini@redhat.com, cornelia.huck@de.ibm.com, wexu@redhat.com,
	vkaplans@redhat.com, alex.williamson@redhat.com,
	peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/3] Introduce IOMMUNotifier struct
Date: Tue,  6 Sep 2016 21:24:24 +0800	[thread overview]
Message-ID: <1473168267-25673-1-git-send-email-peterx@redhat.com> (raw)

This is merely a re-written for v1 (so no change log provided)... But
anyway let's call it v2.

The idea originates from one of Alex's reply:

  https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg00254.html

But after further discussions, it seems that only adding a simple type
for notifier is not enough. This series introduced IOMMUNotifier
struct to replace the old Notifier interface. Along with it, we can
provide registration for one (or multiple) of the IOMMU notifications:

- cache invalidations
- entry changes

This is a support material for Jason's vhost dmar patchset.

Please read commit messages for detailed information. Thanks,

Peter Xu (3):
  memory: introduce IOMMUNotifier and its caps
  memory: generalize iommu_ops.notify_started to notifier_add
  intel_iommu: allow invalidation typed notifiers

 hw/i386/intel_iommu.c         | 16 +++++++++------
 hw/ppc/spapr_iommu.c          | 18 +++++++++++------
 hw/vfio/common.c              |  5 +++--
 include/exec/memory.h         | 45 +++++++++++++++++++++++++++++++++----------
 include/hw/ppc/spapr.h        |  1 +
 include/hw/vfio/vfio-common.h |  2 +-
 memory.c                      | 45 ++++++++++++++++++++++++++++++-------------
 7 files changed, 94 insertions(+), 38 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-06 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 13:24 Peter Xu [this message]
2016-09-06 13:24 ` [Qemu-devel] [PATCH v2 1/3] memory: introduce IOMMUNotifier and its caps Peter Xu
2016-09-06 14:29   ` Paolo Bonzini
2016-09-07  4:55     ` Peter Xu
2016-09-06 13:24 ` [Qemu-devel] [PATCH v2 2/3] memory: generalize iommu_ops.notify_started to notifier_add Peter Xu
2016-09-06 13:24 ` [Qemu-devel] [PATCH v2 3/3] intel_iommu: allow invalidation typed notifiers 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=1473168267-25673-1-git-send-email-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=dgibson@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vkaplans@redhat.com \
    --cc=wexu@redhat.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 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.