From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com, jerin.jacob@caviumnetworks.com,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: [dpdk-dev] [PATCH v2] qat: fix for VFs not getting recognized
Date: Mon, 20 Jun 2016 17:10:11 +0100 [thread overview]
Message-ID: <1466439011-88009-1-git-send-email-deepak.k.jain@intel.com> (raw)
In-Reply-To: <1466087775-235077-1-git-send-email-deepak.k.jain@intel.com>
Updated the code to use RTE_PCI_DEVICE.
Fixes: 701c8d80c820 ("pci: support class id probing")
Signed-off-by: Jain, Deepak K <deepak.k.jain@intel.com>
---
drivers/crypto/qat/rte_qat_cryptodev.c | 10 +++-------
lib/librte_eal/common/include/rte_pci_dev_ids.h | 10 ++++++++++
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/crypto/qat/rte_qat_cryptodev.c b/drivers/crypto/qat/rte_qat_cryptodev.c
index a7912f5..31d3c0c 100644
--- a/drivers/crypto/qat/rte_qat_cryptodev.c
+++ b/drivers/crypto/qat/rte_qat_cryptodev.c
@@ -68,13 +68,9 @@ static struct rte_cryptodev_ops crypto_qat_ops = {
*/
static struct rte_pci_id pci_id_qat_map[] = {
- {
- .vendor_id = 0x8086,
- .device_id = 0x0443,
- .subsystem_vendor_id = PCI_ANY_ID,
- .subsystem_device_id = PCI_ANY_ID
- },
- {.device_id = 0},
+#define RTE_PCI_DEV_ID_DECL_QATVF(vend, dev) {RTE_PCI_DEVICE(vend, dev)},
+#include "rte_pci_dev_ids.h"
+{.device_id = 0},
};
static int
diff --git a/lib/librte_eal/common/include/rte_pci_dev_ids.h b/lib/librte_eal/common/include/rte_pci_dev_ids.h
index cf7b548..a4fc430 100644
--- a/lib/librte_eal/common/include/rte_pci_dev_ids.h
+++ b/lib/librte_eal/common/include/rte_pci_dev_ids.h
@@ -152,6 +152,10 @@
#define RTE_PCI_DEV_ID_DECL_BNX2XVF(vend, dev)
#endif
+#ifndef RTE_PCI_DEV_ID_DECL_QATVF
+#define RTE_PCI_DEV_ID_DECL_QATVF(vend, dev)
+#endif
+
#ifndef PCI_VENDOR_ID_INTEL
/** Vendor ID used by Intel devices */
#define PCI_VENDOR_ID_INTEL 0x8086
@@ -615,6 +619,12 @@ RTE_PCI_DEV_ID_DECL_I40EVF(PCI_VENDOR_ID_INTEL, I40E_DEV_ID_X722_A0_VF)
RTE_PCI_DEV_ID_DECL_I40EVF(PCI_VENDOR_ID_INTEL, I40E_DEV_ID_X722_VF)
RTE_PCI_DEV_ID_DECL_I40EVF(PCI_VENDOR_ID_INTEL, I40E_DEV_ID_X722_VF_HV)
+/****************** Intel QuickAssist(QAT) Device ******************/
+
+#define QAT_DEV_ID_895XCC_VF 0x0443
+
+RTE_PCI_DEV_ID_DECL_QATVF(PCI_VENDOR_ID_INTEL, QAT_DEV_ID_895XCC_VF)
+
/****************** Virtio devices from virtio.h ******************/
#define QUMRANET_DEV_ID_VIRTIO 0x1000
--
2.5.5
next parent reply other threads:[~2016-06-20 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466087775-235077-1-git-send-email-deepak.k.jain@intel.com>
2016-06-20 16:10 ` Jain, Deepak K [this message]
2016-06-20 17:08 ` Thomas Monjalon
2016-06-21 9:03 ` [dpdk-dev] [PATCH v3] " Deepak Kumar Jain
2016-06-21 13:37 ` Thomas Monjalon
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=1466439011-88009-1-git-send-email-deepak.k.jain@intel.com \
--to=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pablo.de.lara.guarch@intel.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).