qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Jia He <hejianet@gmail.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Questio] What the proper vfio NIC for emulation smmu?
Date: Fri, 22 Jun 2018 08:39:33 +0200	[thread overview]
Message-ID: <90a232ff-74f7-8d10-74f4-87a0008c41df@redhat.com> (raw)
In-Reply-To: <d5f8be99-9602-a628-bc43-486e7befc4dc@gmail.com>

Hello Jia,

On 06/22/2018 03:44 AM, Jia He wrote:
> Hi Eric
> I want to test your smmu emulation patchset with vfio-pci ethernet device.
> Could you kindly give me the NIC type information.
> In my test, there is vf probe error for menallox connect 4 NIC and TX Unit
> hang error for Intel X540 NIC. That's the reason why I ask this question.
> 
virtual SMMUv3 is not integrated with VFIO and is not planned to be. It
was tested with virtio-net-pci (without vhost-net).

With upstream code you should see the following warning:

"SMMUV3 does not support vhost/vfio integration yet: devices of those
types will not function properly"

With "[PATCH v3 0/4] ARM SMMUv3: IOTLB Emulation and VHOST Support",
vhost-net gets integrated. VFIO won't be integrated either. If vfio-pci
device are attempted to be used along with vsmmu, you will get
"SMMUv3 does not support notification on MAP: device %s will not
function properly"

My attempt to integrate the vsmmu with VFIO in the same manner as intel
iommu (using a fake caching mode) was rejected by the kernel maintainer.
So for VFIO use case, we need either 2 stage enablement (not implemented
yet) or virtio-iommu. I will respin this latter against v0.7 spec
probably next week.

Thanks

Eric

  reply	other threads:[~2018-06-22  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  1:44 [Qemu-devel] [Questio] What the proper vfio NIC for emulation smmu? Jia He
2018-06-22  6:39 ` Auger Eric [this message]
2018-06-22  7:05   ` Jia He

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=90a232ff-74f7-8d10-74f4-87a0008c41df@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=hejianet@gmail.com \
    --cc=qemu-arm@nongnu.org \
    --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 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).