public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol•org>
To: Alexander Duyck <alexander.h.duyck@intel•com>
Cc: Chris Wright <chrisw@sous-sol•org>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	"Ronciak, John" <john.ronciak@intel•com>,
	"e1000-devel@lists•sourceforge.net"
	<e1000-devel@lists•sourceforge.net>
Subject: Re: igb VF allocation with quirk_i82576_sriov
Date: Tue, 22 Sep 2009 22:12:56 -0700	[thread overview]
Message-ID: <20090923051256.GA32596@sequoia.sous-sol.org> (raw)
In-Reply-To: <4AB8F042.4030306@intel.com>

* Alexander Duyck (alexander.h.duyck@intel•com) wrote:
> Chris Wright wrote:
>> Is this known to work?  During recent virt testing for upcoming Fedora 12,
>> a box w/out SR-IOV support in BIOS was using quirk to create VF BAR space,
>> VF allocation worked enough to assign a device to the guest, but igbvf
>> was not actually functioning properly in the guest.
>>
>> Is it worth debugging this further, or is it already a known issue?
>
> You could be experiencing one of a couple different issues.
>
> First when you say you started SR-IOV on a box w/out SR-IOV support I  
> assume you are using "pci=assign-busses" in order to reserve the bus  
> space for the VFs, is that correct?  Also while your system may not  
> support SR-IOV does it at least support VT-d?  Without VT-d support you  
> won't be able to assign a device to the guest.

VT-d was definitely there, as for the rest I'll have to ask the tester
for more details.  I just wanted to verify that it's a known working
combo before spending more time on it.

Regarding the bus numbering, I don't think there's a bus issue.
The PF+VFs all stay w/in same bus segment despite large offset and the
stride (IIRC, this was only device on bus 2, a dual port igb on .0 and .1.
the offset is 128 and stride is 2, so even w/ 8 VFs the max device would
be something like 2:11.7 or 2:12.0).

> My recommendations for further testing would be to test a VF on the host  
> kernel to see if that works.  If it does then you could also try direct  
> assigning an entire port to see if that works.  If the entire port  
> doesn't work then you probably don't have VT-d enabled.

Yeah, IIRC, igbvf at least loaded on the host (on the guest too, after
unbinding host driver).  I didn't get a chance to see if VF passed
traffic on the host, and from the report, it wasn't able to get a dhcp
address in the guest.  Will dig into it a bit more after plumbers.

thanks,
-chris

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf

      reply	other threads:[~2009-09-23  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  5:19 igb VF allocation with quirk_i82576_sriov Chris Wright
2009-09-22 15:41 ` Alexander Duyck
2009-09-23  5:12   ` Chris Wright [this message]

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=20090923051256.GA32596@sequoia.sous-sol.org \
    --to=chrisw@sous-sol$(echo .)org \
    --cc=alexander.h.duyck@intel$(echo .)com \
    --cc=e1000-devel@lists$(echo .)sourceforge.net \
    --cc=john.ronciak@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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