DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Aashima Arora <arora.aa91@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Accessing a Virtual Function Driver in Guest Machine via	VFIO
Date: Wed, 10 Dec 2014 07:12:27 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286C9E62D@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKARMmja9UpFc1YJ3X7NHAJ2yjLA4DGrOAXb_uNRfq14S39eKw@mail.gmail.com>

On 12/6/2014 3:01 AM, Aashima Arora wrote:
> Hi,
> I was trying to access the pci config space(BAR) of the virtual function
> device visible in the virtual machine, similar to what DPDK does on host
> via both UIO and VFIO. Did the following steps.
>
> 1. Bound PF Drivers to ixgbe and spawned virtual function drivers , bound
> them to vfio-pci and set their mac addresses via ip link.  Ran Qemu and
> assigned the VF Device using vfio-pci device assignment and initialized the
> virtual machine.
> insmod igb max_vfs=2
>
> ./x86_64-softmmu/qemu-system-x86_64 -cpu host -boot c -hda
> /home/vm-images/vm2.imgsnapshot -m 2048M -smp 2 --enable-kvm -name 'vm2'
> -vnc :2 -pidfile /tmp/vm2.pid -driile=fat:rw:/tmp/share,snapshot=off
> -device vfio-pci,host=01:10.1,id=net1
>
>
> 2.  The VF Device was visible with another pci address.
>
> 00:04.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+
> Network
> Connection (rev 01)
>
> Further ran DPDK testpmd on top of VM but bound the virtual function driver
> to igb_uio instead of vfio-pci. It ran successfully.  The ixgbevf pmd
> driver is able to access the BAR registers in pci_uio_map_resource via
> mmaping somewhere close to hugepages. I was not able to bind the virtual
> function driver in VM to vfio-pci and hence DPDK would not be able to run
> with VFIO enabled as it complains of no IOMMU support. I also believe that
> there is little logic in binding the vf device to vfio-pci again since qemu
> has already taken care of it and hardware support is involved.
>
> So my questions are
> a. vfio is meant to be  a replacement for both uio and device assignment
> for qemu. This doesnt seem simultaneous. Comment?

What do you mean "device assignment" ? You mean pass-through? 
> b. Is there any way to access VF device  using VFIO in guest userspace?
> Have you run DPDK in guest machine with VFIO support enabled and all
> dependent modules inserted and did it work?

As I knows, the answer is *NO*,  because the iommu is not support in guest.
> c. Is igb_uio or uio_pci_generic in future the only way  to access the
> device in guest userspace?

It depends, who knows what will happen in future :)

Thanks,
Michael
> *Regards*
>


  parent reply	other threads:[~2014-12-10  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 19:00 Aashima Arora
     [not found] ` <CY1PR0501MB1418283E203637343060EE08AE620@CY1PR0501MB1418.namprd05.prod.outlook.com>
2014-12-10  6:47   ` Aashima Arora
2014-12-10  7:12 ` Qiu, Michael [this message]
2014-12-10  7:24   ` Aashima Arora

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=533710CFB86FA344BFBF2D6802E60286C9E62D@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=arora.aa91@gmail.com \
    --cc=dev@dpdk.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).