From: Ben Hutchings <bhutchings@solarflare.com>
To: Rick Jones <raj@tardy.cup.hp.com>
Cc: <netdev@vger.kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
Michael Tsirkin <mst@redhat.com>,
<virtualization@lists.linux-foundation.org>
Subject: Re: [RFC PATCH net-next] enable virtio_net to return bus_info in ethtool -i consistent with emulated NICs
Date: Mon, 14 Nov 2011 22:30:00 +0000 [thread overview]
Message-ID: <1321309800.2827.22.camel@bwh-desktop> (raw)
In-Reply-To: <20111114215241.5B8BF2900307@tardy>
On Mon, 2011-11-14 at 13:52 -0800, Rick Jones wrote:
> From: Rick Jones <rick.jones2@hp.com>
>
> Add a new .bus_name to virtio_config_ops then modify virtio_net to
> call through to it in an ethtool .get_drvinfo routine to report
> bus_info in ethtool -i output which is consistent with other
> emulated NICs and the output of lspci.
[...]
> diff --git a/drivers/lguest/lguest_device.c b/drivers/lguest/lguest_device.c
> index 0dc30ff..3724d45 100644
> --- a/drivers/lguest/lguest_device.c
> +++ b/drivers/lguest/lguest_device.c
> @@ -381,6 +381,11 @@ error:
> return PTR_ERR(vqs[i]);
> }
>
> +static const char *lg_bus_name(struct virtio_device *vdev)
> +{
> + return "Not Implemented";
> +}
[...]
> +static const char *kvm_bus_name(struct virtio_device *vdev)
> +{
> + return "Not Implemented";
> +}
[...]
Please use the existing 'not implemented' value, which is the empty
string. If you think ethtool should print some helpful message instead
of an empty string, please submit a patch for ethtool.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-11-14 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 21:52 [RFC PATCH net-next] enable virtio_net to return bus_info in ethtool -i consistent with emulated NICs Rick Jones
2011-11-14 22:30 ` Ben Hutchings [this message]
2011-11-14 22:40 ` Rick Jones
2011-11-15 0:06 ` Rick Jones
2011-11-15 0:10 ` Ben Hutchings
2011-11-15 0:14 ` Rick Jones
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=1321309800.2827.22.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=raj@tardy.cup.hp.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).