From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Griffin, John" <john.griffin@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] qat: fix for VFs not getting recognized
Date: Thu, 16 Jun 2016 16:25:50 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C903393C2D06@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <11386705.985BuDGx4F@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, June 16, 2016 5:16 PM
> To: Jain, Deepak K <deepak.k.jain@intel.com>
> Cc: dev@dpdk.org; Griffin, John <john.griffin@intel.com>; De Lara Guarch,
> Pablo <pablo.de.lara.guarch@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] qat: fix for VFs not getting recognized
>
> 2016-06-16 16:29, Jain, Deepak K:
> > Due to addition of CLASS_ID in EAL, class_id is amended into the code.
>
> Why the VF is not recognized?
> The class id should not be mandatory.
Without the change proposed, QuickAssist Devices were not visible and hence tests were not running.
Seems like changes in EAL especially where class_id is added affected the QuickAssist tests.
With this change, QuickAssist devices are visible during tests and tests working fine.
next prev parent reply other threads:[~2016-06-16 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 15:29 Jain, Deepak K
2016-06-16 16:15 ` Thomas Monjalon
2016-06-16 16:25 ` Jain, Deepak K [this message]
2016-06-17 8:18 ` Thomas Monjalon
2016-06-17 9:42 ` Jerin Jacob
2016-06-20 12:59 ` Thomas Monjalon
2016-06-17 9:49 ` Jain, Deepak K
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=A09C9DDE180C7E429EC68E2BFB95C903393C2D06@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.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).