From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bhavesh@vmware.com>
Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com
 [208.91.2.12]) by dpdk.org (Postfix) with ESMTP id 7223D6AA8
 for <dev@dpdk.org>; Fri, 10 May 2013 23:00:00 +0200 (CEST)
Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com
 [10.113.161.71])
 by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 77C9A286CD;
 Fri, 10 May 2013 14:00:00 -0700 (PDT)
Received: from zcs-prod-mta-3.vmware.com (zcs-prod-mta-3.vmware.com
 [10.113.163.65])
 by sc9-mailhost1.vmware.com (Postfix) with ESMTP id 724F01870C;
 Fri, 10 May 2013 14:00:00 -0700 (PDT)
Received: from zcs-prod-mta-3.vmware.com (localhost.localdomain [127.0.0.1])
 by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP id 58B99E005F;
 Fri, 10 May 2013 14:00:00 -0700 (PDT)
Received: from zcs-prod-mbox-7.vmware.com (lbv-sc9-t2prod2-int.vmware.com
 [10.113.160.246]) by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP;
 Fri, 10 May 2013 14:00:00 -0700 (PDT)
Date: Fri, 10 May 2013 14:00:00 -0700 (PDT)
From: Bhavesh Davda <bhavesh@vmware.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Message-ID: <1681866850.5680257.1368219600105.JavaMail.root@vmware.com>
In-Reply-To: <20130510122929.0ff687aa@nehalam.linuxnetplumber.net>
References: <AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0D@xmb-aln-x05.cisco.com>
 <CAE68AUOr7B5a2QvduJhH0kEHPi+sR9X3qfrtumgLxT1BK4VS+Q@mail.gmail.com>
 <1676591087.5291867.1368201908283.JavaMail.root@vmware.com>
 <20130510091549.3c064df6@nehalam.linuxnetplumber.net>
 <525534677.5312512.1368202896189.JavaMail.root@vmware.com>
 <20130510114450.7104c5d2@nehalam.linuxnetplumber.net>
 <69354296.5541435.1368213042137.JavaMail.root@vmware.com>
 <20130510122929.0ff687aa@nehalam.linuxnetplumber.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.113.163.67]
X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC26 (Mac)/8.0.3_GA_5664)
Thread-Topic: rte_eth_dev_count() returns 0
Thread-Index: WnDVftHuN2D5mrmyyTuCVCrIHw5cSQ==
Cc: Henry Wang <wang_hr@neusoft.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 21:00:01 -0000

> From: "Stephen Hemminger" <stephen@networkplumber.org>
> Sent: Friday, May 10, 2013 12:29:29 PM
> 
> On Fri, 10 May 2013 12:10:42 -0700 (PDT)
> Bhavesh Davda <bhavesh@vmware.com> wrote:
> 
> > Hi Stephen,
> > 
> > I checked both our hypervisor code and with the experts who wrote and
> > maintain the code, and we don't have any such limitation about not
> > supporting SR-IOV if the motherboard or device doesn't support PCIe ASPM.
> > 
> > If you can point me to the Intel person(s) who gave you that information
> > (offline, no need to make this public :)), we can make sure such FUD
> > doesn't continue getting spread too far.
> > 
> > Thanks for making us aware of this FUD though.
> > 
> > --
> > Bhavesh Davda
> > 
> 
> According to Intel the problem was that the BIOS did not support _OSC table.
> SR-IOV needs VT-d enabled and BIOS with _OSC and DMA ACPI tables.
> The _OSC table is an ACPI control method that the kernel uses to interact
> with PCIe Active Statep Power Management. Linux just assume no  ASPM if table
> is missing, VMWare ESX 5.1 seems to need it
> 

Once again, both in looking at our ACPI _OSC code in the hypervisor and in consulting with the experts, there is no such limitation for SR-IOV support in ESXi.

Regards

- Bhavesh