From: Laszlo Ersek <lersek@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] xennet_get_drvinfo()
Date: Wed, 24 Nov 2010 21:47:32 +0100 [thread overview]
Message-ID: <4CED79E4.4030608@redhat.com> (raw)
In-Reply-To: <4CED7792.1090600@goop.org>
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@solarflare.com>
> 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
next prev parent reply other threads:[~2010-11-24 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 18:03 [PATCH] xennet_get_drvinfo() Laszlo Ersek
2010-11-11 18:50 ` Ian Campbell
2010-11-24 20:37 ` Jeremy Fitzhardinge
2010-11-24 20:47 ` Laszlo Ersek [this message]
2010-11-24 20:56 ` Jeremy Fitzhardinge
2010-11-24 21:37 ` VGA console low power mode in Xen Carsten Schiers
2010-11-25 10:56 ` Stefano Stabellini
2010-11-25 10:17 ` [PATCH] xennet_get_drvinfo() Ian Campbell
2010-11-25 19:15 ` Jeremy Fitzhardinge
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=4CED79E4.4030608@redhat.com \
--to=lersek@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.