From: Auger Eric <eric.auger@redhat.com>
To: Bharat Bhushan <bharatb.yadav@gmail.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"drjones@redhat.com" <drjones@redhat.com>,
Tomasz Nowicki <tnowicki@marvell.com>,
"mst@redhat.com" <mst@redhat.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Bharat Bhushan <bharatb.linux@gmail.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"linu.cherian@cavium.com" <linu.cherian@cavium.com>,
"linuc.decode@gmail.com" <linuc.decode@gmail.com>,
"eric.auger.pro@gmail.com" <eric.auger.pro@gmail.com>
Subject: Re: [Qemu-devel] [PATCH RFC v5 0/5] virtio-iommu: VFIO integration
Date: Mon, 2 Mar 2020 08:00:03 +0100 [thread overview]
Message-ID: <7393a1e7-d5ea-c87f-6f36-6e4e8ad2d8e7@redhat.com> (raw)
In-Reply-To: <CAHS=5b3g_6rHzFvF4-RDu2cn_tsP4TmJp+rFxPgiWpo-2kdnYA@mail.gmail.com>
Hi Bharat,
On 3/2/20 6:12 AM, Bharat Bhushan wrote:
>
> Hi Eric,
>
> On Fri, Feb 28, 2020 at 3:06 PM Auger Eric <eric.auger@redhat.com
> <mailto:eric.auger@redhat.com>> wrote:
>
> Hi Bharat,
>
> On 11/27/18 7:52 AM, Bharat Bhushan wrote:
> > This patch series integrates VFIO with virtio-iommu. This is
> > tested with assigning 2 pci devices to Virtual Machine.
> >
> > This version is mainly about rebasing on v9 version on
> > virtio-iommu device framework from Eric Augur.
> >
> > This patch series allows PCI pass-through using virtio-iommu.
> >
> > This series is based on:
> > - virtio-iommu kernel driver by Jean-Philippe Brucker
> > [PATCH v5 0/7] Add virtio-iommu driver
> > git://linux-arm.org/kvmtool-jpb.git
> <http://linux-arm.org/kvmtool-jpb.git> virtio-iommu/v0.9
> >
> > - virtio-iommu device emulation by Eric Augur.
> > [RFC,v9,00/17] VIRTIO-IOMMU device
> > https://github.com/eauger/qemu/tree/v3.1.0-rc2-virtio-iommu-v0.9
>
> Now we have the driver and the base qemu device upstream we may resume
> this activity to complete the VFIO integration. Do you intend the
> respin? Otherwise let me know if you want me to help.
>
>
> Yes Eric, I am planning to respin the changes.
>
> Can you please point to latest changes (qemu/Linux both).
the driver and the base qemu device are upstream. This only boots in DT
mode at the moment with machvirt. Use -virtio-iommu-pci to instantiate
the device. About the qemu device, you will find latest changes in the
v16 history log: https://patchwork.kernel.org/cover/11382271/
Thanks
Eric
>
> Thanks
> -Bharat
>
> Thanks
>
> Eric
> >
> > v4->v5:
> > - Rebase to v9 version from Eric
> > - PCIe device hotplug fix
> > - Added Patch 1/5 from Eric previous series (Eric somehow dropped in
> > last version.
> > - Patch "Translate the MSI doorbell in kvm_arch_fixup_msi_route"
> > already integrated with vsmmu3
> >
> > v3->v4:
> > - Rebase to v4 version from Eric
> > - Fixes from Eric with DPDK in VM
> > - Logical division in multiple patches
> >
> > v2->v3:
> > - This series is based on "[RFC v3 0/8] VIRTIO-IOMMU device"
> > Which is based on top of v2.10-rc0 that
> > - Fixed issue with two PCI devices
> > - Addressed review comments
> >
> > v1->v2:
> > - Added trace events
> > - removed vSMMU3 link in patch description
> >
> > Bharat Bhushan (4):
> > virtio-iommu: Add iommu notifier for iommu-map/unmap
> > virtio-iommu: Call iommu notifier on attach/detach
> > virtio-iommu: add virtio-iommu replay
> > virtio-iommu: handle IOMMU Notifier flag changes
> >
> > Eric Auger (1):
> > hw/vfio/common: Do not print error when viommu translates into
> an mmio
> > region
> >
> > hw/vfio/common.c | 2 -
> > hw/virtio/trace-events | 5 +
> > hw/virtio/virtio-iommu.c | 190
> ++++++++++++++++++++++++++++++-
> > include/hw/virtio/virtio-iommu.h | 6 +
> > 4 files changed, 198 insertions(+), 5 deletions(-)
> >
>
>
>
> --
> -Bharat
prev parent reply other threads:[~2020-03-02 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 6:52 [Qemu-devel] [PATCH RFC v5 0/5] virtio-iommu: VFIO integration Bharat Bhushan
2018-11-27 6:52 ` [Qemu-devel] [PATCH RFC v5 1/5] hw/vfio/common: Do not print error when viommu translates into an mmio region Bharat Bhushan
2018-11-27 6:52 ` [Qemu-devel] [PATCH RFC v5 2/5] virtio-iommu: Add iommu notifier for iommu-map/unmap Bharat Bhushan
2018-11-27 6:52 ` [Qemu-devel] [PATCH RFC v5 3/5] virtio-iommu: Call iommu notifier on attach/detach Bharat Bhushan
2018-11-27 6:52 ` [Qemu-devel] [PATCH RFC v5 4/5] virtio-iommu: add virtio-iommu replay Bharat Bhushan
2018-11-27 6:53 ` [Qemu-devel] [PATCH RFC v5 5/5] virtio-iommu: handle IOMMU Notifier flag changes Bharat Bhushan
2020-02-28 9:36 ` [Qemu-devel] [PATCH RFC v5 0/5] virtio-iommu: VFIO integration Auger Eric
2020-03-02 5:12 ` Bharat Bhushan
2020-03-02 7:00 ` Auger Eric [this message]
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=7393a1e7-d5ea-c87f-6f36-6e4e8ad2d8e7@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bharatb.linux@gmail.com \
--cc=bharatb.yadav@gmail.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=kevin.tian@intel.com \
--cc=linu.cherian@cavium.com \
--cc=linuc.decode@gmail.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tnowicki@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).