From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Alexander Graf <agraf@suse.de>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
Mitch Williams <mitch.a.williams@intel.com>,
Andy Gospodarek <andy@greyhouse.net>,
Stefan Assmann <sassmann@kpanic.de>,
Aaron Brown <aaron.f.brown@intel.com>,
Greg Rose <gregory.v.rose@intel.com>,
John Ronciak <john.ronciak@intel.com>
Subject: Re: [PATCH] igb: Indicate failure on vf reset for empty mac address
Date: Thu, 09 Oct 2014 15:34:54 +0400 [thread overview]
Message-ID: <543672DE.80202@cogentembedded.com> (raw)
In-Reply-To: <1412803407-10621-1-git-send-email-agraf@suse.de>
Hello.
On 10/9/2014 1:23 AM, Alexander Graf wrote:
> Commit 5ac6f91d changed the igb driver to expose a zero (empty) mac
Please also specify that commit's summary line in parens.
> address to the VF on reset rather than a random one.
> However, that behavioral change also requires igbvf driver changes
> which can be hard especially when we want to talk to proprietary
> guest OSs.
> Looking at the code previous to the commit in Linux that made igbvf
> work with empty mac addresses (8d56b6d), we can see that on reset
And that one's
> failure the driver will try to generate a new mac address with both
> the old and the new code.
> Furthermore, ixgbe does send reset failure when it detects an empty
> mac address (35055928c).
And that one's too.
> So I think it's safe to make igb behave the same. With this patch I
> can successfully run a Windows 8.1 guest with an empty mac address
> and an assigned igbvf device that has no mac address set by the host.
> If anyone is aware of a guest driver that chokes on NACK returns of
> VF RESET commands, please speak up.
> Signed-off-by: Alexander Graf <agraf@suse.de>
WBR, Sergei
prev parent reply other threads:[~2014-10-09 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 21:23 [PATCH] igb: Indicate failure on vf reset for empty mac address Alexander Graf
2014-10-08 21:29 ` Jeff Kirsher
2014-10-08 21:32 ` Jeff Kirsher
2014-10-08 22:03 ` Alexander Graf
2014-10-08 22:29 ` Jeff Kirsher
2014-10-08 22:38 ` Alexander Graf
2014-10-08 23:33 ` Williams, Mitch A
2014-10-08 23:45 ` Alexander Graf
2014-10-09 11:34 ` Sergei Shtylyov [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=543672DE.80202@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=aaron.f.brown@intel.com \
--cc=agraf@suse.de \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@kpanic.de \
/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).