From: "Rose, Gregory V" <gregory.v.rose@intel.com>
To: David Ahern <daahern@cisco.com>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>
Subject: RE: VFs go missing with latest kernel
Date: Wed, 1 Feb 2012 18:02:58 +0000 [thread overview]
Message-ID: <C5551D9AAB213A418B7FD5E4A6F30A0702F66B42@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <4F297D25.7090902@cisco.com>
> -----Original Message-----
> From: David Ahern [mailto:daahern@cisco.com]
> Sent: Wednesday, February 01, 2012 9:58 AM
> To: Rose, Gregory V
> Cc: 'LKML'
> Subject: Re: VFs go missing with latest kernel
>
> On 02/01/2012 10:47 AM, Rose, Gregory V wrote:
> > I found this in the log file you sent me. I had missed it yesterday.
> >
> > [ 15.835223] igb 0000:07:00.0: 7 pre-allocated VFs found - override
> max_vfs setting of 7
> > [ 15.835393] igb 0000:07:00.0: 7 VFs allocated
> >
> > I think that must be a bug in the code that searches for VFs already
> allocated and is the source of your problem. I'll keep you updated on
> what I find but it has to be a bug in the VF device lookups.
>
> Confused. What is pre-allocating the VFs during boot? Looking at my
> rc-scripts I am only set MAC addresses at boot. No VMs have been started
> yet. This setup has worked fine with Fedora 14 and 3.0 kernels; it's
> really the move to 3.3-rc that I hit the problem.
Nothing is pre-allocating the VFs. That is the bug, the function I wrote to find pre-allocated VFs is messed up somehow. Since it (mistakenly) thinks it's already found pre-allocated VFs, it doesn't call pci_enable_sriov() to allocate them.
- Greg
prev parent reply other threads:[~2012-02-01 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 22:53 VFs go missing with latest kernel David Ahern
2012-01-31 22:58 ` Rose, Gregory V
2012-01-31 23:05 ` David Ahern
2012-01-31 23:07 ` Rose, Gregory V
2012-02-01 0:30 ` David Ahern
2012-02-01 0:43 ` Rose, Gregory V
2012-02-01 0:50 ` David Ahern
2012-02-01 1:03 ` Rose, Gregory V
2012-02-01 17:47 ` Rose, Gregory V
2012-02-01 17:57 ` David Ahern
2012-02-01 18:02 ` Rose, Gregory V [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=C5551D9AAB213A418B7FD5E4A6F30A0702F66B42@ORSMSX106.amr.corp.intel.com \
--to=gregory.v.rose@intel.com \
--cc=daahern@cisco.com \
--cc=linux-kernel@vger.kernel.org \
/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).