From: Bhavesh Davda <bhavesh@vmware.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Henry Wang <wang_hr@neusoft.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0
Date: Fri, 10 May 2013 14:00:00 -0700 (PDT) [thread overview]
Message-ID: <1681866850.5680257.1368219600105.JavaMail.root@vmware.com> (raw)
In-Reply-To: <20130510122929.0ff687aa@nehalam.linuxnetplumber.net>
> 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
next prev parent reply other threads:[~2013-05-10 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 1:00 Rui Vaz (ruvaz)
2013-05-10 1:18 ` Henry Wang
2013-05-10 16:05 ` Bhavesh Davda
2013-05-10 16:15 ` Stephen Hemminger
2013-05-10 16:21 ` Bhavesh Davda
2013-05-10 18:44 ` Stephen Hemminger
2013-05-10 19:10 ` Bhavesh Davda
2013-05-10 19:29 ` Stephen Hemminger
2013-05-10 21:00 ` Bhavesh Davda [this message]
2013-05-18 0:09 ` Rui Vaz (ruvaz)
2013-05-10 15:47 ` Vincent JARDIN
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=1681866850.5680257.1368219600105.JavaMail.root@vmware.com \
--to=bhavesh@vmware.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=wang_hr@neusoft.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).