All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cindy Lu <lulu@redhat.com>
To: lulu@redhat.com, alex.williamson@redhat.com, jasowang@redhat.com,
	mst@redhat.com, pbonzini@redhat.com, peterx@redhat.com,
	david@redhat.com, f4bug@amsat.org, sgarzare@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [PATCH v4 0/2] vhost-vdpa: add support for vIOMMU
Date: Thu, 27 Oct 2022 15:40:30 +0800	[thread overview]
Message-ID: <20221027074032.1101939-1-lulu@redhat.com> (raw)

These patches are to support vIOMMU in vdpa device

changes in V3
1. Move function vfio_get_xlat_addr to memory.c
2. Use the existing memory listener, while the MR is
iommu MR then call the function iommu_region_add/
iommu_region_del

changes in V4
1.make the comments in vfio_get_xlat_addr more general

Cindy Lu (2):
  vfio: move the function vfio_get_xlat_addr() to memory.c
  vhost-vdpa: add support for vIOMMU

 hw/vfio/common.c               |  92 +----------------------
 hw/virtio/vhost-vdpa.c         | 131 ++++++++++++++++++++++++++++++---
 include/exec/memory.h          |   4 +
 include/hw/virtio/vhost-vdpa.h |  10 +++
 softmmu/memory.c               |  84 +++++++++++++++++++++
 5 files changed, 222 insertions(+), 99 deletions(-)

-- 
2.34.3



             reply	other threads:[~2022-10-27  7:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  7:40 Cindy Lu [this message]
2022-10-27  7:40 ` [PATCH v4 1/2] vfio: move the function vfio_get_xlat_addr() to memory.c Cindy Lu
2022-10-27  8:11   ` Jason Wang
2022-10-27 15:30   ` Peter Xu
2022-10-27 21:11   ` Alex Williamson
2022-10-28  1:50     ` Jason Wang
2022-10-28  2:08       ` Alex Williamson
2022-10-28  2:23         ` Jason Wang
2022-10-28  2:35           ` Alex Williamson
2022-10-28  2:40             ` Jason Wang
2022-10-27  7:40 ` [PATCH v4 2/2] vhost-vdpa: add support for vIOMMU Cindy Lu
2022-10-27  8:10   ` Jason Wang
2022-10-29  7:57 ` [PATCH v4 0/2] " Michael S. Tsirkin
2022-10-29  7:58   ` Cindy Lu

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=20221027074032.1101939-1-lulu@redhat.com \
    --to=lulu@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=david@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@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.