DPDK usage discussions
 help / color / mirror / Atom feed
From: Chinmaya Dwibedy <ckdwibedy@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Probing fails upon trying to bind all QAT VFs to igb_uio kernel driver on VM
Date: Thu, 8 Sep 2016 11:08:26 +0530	[thread overview]
Message-ID: <CAMHS8REfayNnYipwXYx0MtVgZm6W4q_TTJ07KP7=bCG+eAbEkQ@mail.gmail.com> (raw)

Hi,

We have installed openstack-mitaka release on CentO7 system. It has two
Intel QAT devices. There are 32 VF devices available
per QAT Device/DH895xCC device.  I have assigned 4 QAT VFs to VM instance
(Wind River Linux).

On VM,

1)  The # lspci -vvd: 443 command confirms that, these QAT VFs are not used
by any kernel driver.

2)  The #lsmod | grep qa also says that, no QAT driver is loaded.

Did #echo "8086 0443" > /sys/bus/pci/drivers/igb_uio/new_id to bind all the
available 4 VFs to the DPDK UIO driver. Thereafter triggered #lspci -vvd:
443 and found that none of the QAT VFs  are bound to  igb_uio kernel
driver. The system log (#dmesg) shows that, probe failed for these devices.

Can anyone please suggest what might be the underlying issue and its
solution? Thank you in advance for your support and time.

root@Local:/opt# dmesg -c

 [ 1979.178546] igb_uio: probe of 0000:00:06.0 failed with error -2

[ 1979.181698] igb_uio: probe of 0000:00:07.0 failed with error -2

[ 1979.184850] igb_uio: probe of 0000:00:08.0 failed with error -2

[ 1979.187997] igb_uio: probe of 0000:00:09.0 failed with error -2

root@Local:/opt#

root@Local:/opt# lspci -vvd:443

00:06.0 Co-processor: Intel Corporation DH895XCC Series QAT Virtual Function

        Subsystem: Intel Corporation Device 0000

        Physical Slot: 6

        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-

        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

        Region 0: Memory at febd7000 (64-bit, non-prefetchable) [size=4K]

        Region 2: Memory at febd8000 (64-bit, non-prefetchable) [size=4K]

        Capabilities: [90] MSI: Enable- Count=1/1 Maskable+ 64bit+

                Address: 0000000000000000  Data: 0000

                Masking: 00000000  Pending: 00000000



00:07.0 Co-processor: Intel Corporation DH895XCC Series QAT Virtual Function

        Subsystem: Intel Corporation Device 0000

        Physical Slot: 7

        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-

        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

        Region 0: Memory at febd9000 (64-bit, non-prefetchable) [size=4K]

        Region 2: Memory at febda000 (64-bit, non-prefetchable) [size=4K]

        Capabilities: [90] MSI: Enable- Count=1/1 Maskable+ 64bit+

                Address: 0000000000000000  Data: 0000

                Masking: 00000000  Pending: 00000000



00:08.0 Co-processor: Intel Corporation DH895XCC Series QAT Virtual Function

        Subsystem: Intel Corporation Device 0000

        Physical Slot: 8

        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-

        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

        Region 0: Memory at febdb000 (64-bit, non-prefetchable) [size=4K]

        Region 2: Memory at febdc000 (64-bit, non-prefetchable) [size=4K]

        Capabilities: [90] MSI: Enable- Count=1/1 Maskable+ 64bit+

                Address: 0000000000000000  Data: 0000

                Masking: 00000000  Pending: 00000000



00:09.0 Co-processor: Intel Corporation DH895XCC Series QAT Virtual Function

        Subsystem: Intel Corporation Device 0000

        Physical Slot: 9

        Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-

        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

        Region 0: Memory at febdd000 (64-bit, non-prefetchable) [size=4K]

        Region 2: Memory at febde000 (64-bit, non-prefetchable) [size=4K]

        Capabilities: [90] MSI: Enable- Count=1/1 Maskable+ 64bit+

                Address: 0000000000000000  Data: 0000

                Masking: 00000000  Pending: 00000000



root@Local:/opt#



Regards,

Chinmaya

                 reply	other threads:[~2016-09-08  5:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAMHS8REfayNnYipwXYx0MtVgZm6W4q_TTJ07KP7=bCG+eAbEkQ@mail.gmail.com' \
    --to=ckdwibedy@gmail.com \
    --cc=users@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).