WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xennet_get_drvinfo()

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xennet_get_drvinfo()
From: Laszlo Ersek <lersek@xxxxxxxxxx>
Date: Wed, 24 Nov 2010 21:47:32 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Wed, 24 Nov 2010 12:46:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CED7792.1090600@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4CDC3003.5040306@xxxxxxxxxx> <1289501456.20667.7.camel@xxxxxxxxxxxxxxxxxxxxx> <4CED7792.1090600@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.6
On 11/24/10 21:37, Jeremy Fitzhardinge wrote:
On 11/11/2010 10:50 AM, Ian Campbell wrote:
On Thu, 2010-11-11 at 18:03 +0000, Laszlo Ersek wrote:
The following patch, written for xen/next-2.6.32, adds get_drvinfo() ("ethtool 
-i") support to netfront. If there is no default get_drvinfo() in effect [0], then 
the patch is intended to remedy the following situation:

   # ethtool -i eth0
   Cannot get driver information: Operation not supported

like this:

   # ethtool -i eth0
   driver: xen-netfront
   version:
   firmware-version:
   bus-info: vif-0

If a default get_drvinfo() is in effect (see [0] again), then the fallback 
works like this:

   # ethtool -i eth0
   driver: vif
   version:
   firmware-version:
   bus-info: vif-0

and it's more fortunate to return the module name ("driver: xen-netfront") than 
"driver: vif".
This is pretty much the same as a patch which I clearly forgot to send a
pull request for ages ago[0] so:

I remember a review comment which suggested it was unnecessary?  Ah, here:

     This should already be covered by:

     commit 01414802054c382072b6cb9a1bdc6e243c74b2d5
     Author: Ben Hutchings<bhutchings@xxxxxxxxxxxxxx>
     Date: Tue Aug 17 02:31:15 2010 -0700

     ethtool: Provide a default implementation of ethtool_ops::get_drvinfo

     Ben.

Maybe I should just cherry-pick that back?

I don't think so, that patch is super-useful.

I knew about that, though. I wrote

>>> The following patch, written for xen/next-2.6.32, adds
>>> get_drvinfo() ("ethtool -i") support to netfront. If there is no
>>> default get_drvinfo() in effect [0], then the patch is intended to
>>> remedy the following situation:

and

>>> If a default get_drvinfo() is in effect (see [0] again), then the
>>> fallback works like this:

and

>>> [0] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=01414802054c382072b6cb9a1bdc6e243c74b2d5#patch17

The fallback does cover the functionality ("driver: vif"), but "driver: xen-netfront" seems to be nicer, because that matches the module (driver) name.

Thanks for considering!
lacos

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel