From: Linu Cherian <linuc.decode@gmail.com>
To: Bharat Bhushan <bharat.bhushan@nxp.com>
Cc: "eric.auger@redhat.com" <eric.auger@redhat.com>,
"eric.auger.pro@gmail.com" <eric.auger.pro@gmail.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"tn@semihalf.com" <tn@semihalf.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"drjones@redhat.com" <drjones@redhat.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"bharatb.yadav@gmail.com" <bharatb.yadav@gmail.com>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH v4 0/5] virtio-iommu: VFIO integration
Date: Wed, 27 Sep 2017 14:28:38 +0530 [thread overview]
Message-ID: <20170927085838.GA32011@virtx40> (raw)
In-Reply-To: <AM5PR0401MB25450ACC804B20D93C4F2D9D9A780@AM5PR0401MB2545.eurprd04.prod.outlook.com>
On Wed Sep 27, 2017 at 08:30:51AM +0000, Bharat Bhushan wrote:
> Hi,
>
> > -----Original Message-----
> > From: Linu Cherian [mailto:linuc.decode@gmail.com]
> > Sent: Wednesday, September 27, 2017 1:11 PM
> > To: Bharat Bhushan <bharat.bhushan@nxp.com>
> > Cc: eric.auger@redhat.com; eric.auger.pro@gmail.com;
> > peter.maydell@linaro.org; alex.williamson@redhat.com; mst@redhat.com;
> > qemu-arm@nongnu.org; qemu-devel@nongnu.org; kevin.tian@intel.com;
> > marc.zyngier@arm.com; tn@semihalf.com; will.deacon@arm.com;
> > drjones@redhat.com; robin.murphy@arm.com; christoffer.dall@linaro.org;
> > bharatb.yadav@gmail.com
> > Subject: Re: [Qemu-arm] [PATCH v4 0/5] virtio-iommu: VFIO integration
> >
> > Hi,
> >
> > On Wed Sep 27, 2017 at 12:03:15PM +0530, Bharat Bhushan wrote:
> > > This patch series integrates VFIO/VHOST with virtio-iommu.
> > >
> > > This version is mainly about rebasing on v4 version on virtio-iommu
> > > device framework from Eric Augur and addresing review comments.
> > >
> > > This patch series allows PCI pass-through using virtio-iommu.
> > >
> > > This series is based on:
> > > - virtio-iommu kernel driver by Jean-Philippe Brucker
> > > [1] [RFC] virtio-iommu version 0.4
> > > git://linux-arm.org/virtio-iommu.git branch viommu/v0.4
> > >
> > > - virtio-iommu device emulation by Eric Augur.
> > > [RFC v4 00/16] VIRTIO-IOMMU device
> > > https://github.com/eauger/qemu/tree/v2.10.0-virtio-iommu-v4
> > >
> > > Changes are available at : https://github.com/bharaty/qemu.git
> > > virtio-iommu-vfio-integration-v4
> > >
> >
> > # With the above sources, was trying to test the vfio-pci device assigned to
> > guest using Qemu.
> > # Both guest and host kernels are configured with 4k as page size.
> > # releavant qemu command snippet,
> > -device virtio-iommu-device -device virtio-blk-device,drive=hd0 \
> > -net none -device vfio-pci,host=xxx
> >
> >
> > On guest booting, observed mutliple messages as below,
> >
> > qemu-system-aarch64: iommu has granularity incompatible with target AS
> >
> > # On adding necessary prints, 0x5000 is len, 0x4fff is address mask
> > and the code expects the address mask to be 0xfff.
>
> I have not seen these errors, I am also using 4K page-size on both host and guest. Can you share compete qemu command and log.
Qemu cmd:
qemu-system-aarch64 -machine virt,gic_version=3 -cpu host -enable-kvm -nographic
-smp 8 -m 1024 -kernel /boot/Image --append "console=ttyAMA0 root=/dev/vda rw"
-drive if=none,file=/home/ubuntu/fs_images/ubu1604.img,id=hd0,format=raw
-device virtio-iommu-device -device virtio-blk-device,drive=hd0 -net none -device vfio-pci,host=0002:01:00.3
Qemu log:
qemu-system-aarch64: iommu has granularity incompatible with target AS
qemu-system-aarch64: iommu has granularity incompatible with target AS
qemu-system-aarch64: iommu has granularity incompatible with target AS
qemu-system-aarch64: iommu has granularity incompatible with target AS
qemu-system-aarch64: iommu has granularity incompatible with target AS
qemu-system-aarch64: iommu has granularity incompatible with target AS
...
>
> Thanks
> -Bharat
>
> >
> > if (len & iotlb->addr_mask) {
> > error_report
> >
> > # vfio_dma_map is failing due to this error.
> >
> > Any pointers ?
> >
> >
> > > 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 (5):
> > > target/arm/kvm: Translate the MSI doorbell in
> > kvm_arch_fixup_msi_route
> > > virtio-iommu: Add iommu notifier for map/unmap
> > > virtio-iommu: Call iommu notifier for attach/detach
> > > virtio-iommu: add iommu replay
> > > virtio-iommu: add iommu notifier memory-region
> > >
> > > hw/virtio/trace-events | 5 ++
> > > hw/virtio/virtio-iommu.c | 181
> > ++++++++++++++++++++++++++++++++++++++-
> > > include/hw/virtio/virtio-iommu.h | 6 ++
> > > target/arm/kvm.c | 27 ++++++
> > > target/arm/trace-events | 3 +
> > > 5 files changed, 219 insertions(+), 3 deletions(-)
> > >
> > > --
> > > 1.9.3
> > >
> > >
> >
> > --
> > Linu cherian
--
Linu cherian
prev parent reply other threads:[~2017-09-27 8:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 6:33 [Qemu-devel] [PATCH v4 0/5] virtio-iommu: VFIO integration Bharat Bhushan
2017-09-27 6:33 ` [Qemu-devel] [PATCH v4 1/5] target/arm/kvm: Translate the MSI doorbell in kvm_arch_fixup_msi_route Bharat Bhushan
2017-09-27 6:33 ` [Qemu-devel] [PATCH v4 2/5] virtio-iommu: Add iommu notifier for map/unmap Bharat Bhushan
2017-09-27 6:33 ` [Qemu-devel] [PATCH v4 3/5] virtio-iommu: Call iommu notifier for attach/detach Bharat Bhushan
2017-09-27 6:33 ` [Qemu-devel] [PATCH v4 4/5] virtio-iommu: add iommu replay Bharat Bhushan
2017-09-27 6:33 ` [Qemu-devel] [PATCH v4 5/5] virtio-iommu: add iommu notifier memory-region Bharat Bhushan
2017-09-27 6:46 ` [Qemu-devel] [PATCH v4 0/5] virtio-iommu: VFIO integration Bharat Bhushan
2017-09-27 7:01 ` Peter Xu
2017-09-27 8:32 ` Bharat Bhushan
2017-09-27 7:41 ` [Qemu-devel] [Qemu-arm] " Linu Cherian
2017-09-27 8:30 ` Bharat Bhushan
2017-09-27 8:55 ` Auger Eric
2017-09-27 9:05 ` Linu Cherian
2017-09-27 9:21 ` Linu Cherian
2017-09-27 9:24 ` Auger Eric
2017-10-04 11:49 ` Linu Cherian
2017-10-05 10:46 ` Auger Eric
2017-10-05 11:54 ` Auger Eric
2017-10-05 12:13 ` Auger Eric
2017-10-05 17:02 ` Auger Eric
2017-10-06 3:46 ` Bharat Bhushan
2017-10-06 7:24 ` Auger Eric
2017-10-06 8:41 ` Linu Cherian
2017-10-10 6:42 ` Bharat Bhushan
2017-10-11 9:42 ` Auger Eric
2017-09-27 8:58 ` Linu Cherian [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=20170927085838.GA32011@virtx40 \
--to=linuc.decode@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=bharat.bhushan@nxp.com \
--cc=bharatb.yadav@gmail.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=kevin.tian@intel.com \
--cc=marc.zyngier@arm.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robin.murphy@arm.com \
--cc=tn@semihalf.com \
--cc=will.deacon@arm.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).