All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] net: Dump client type 'info network'
Date: Fri, 20 May 2011 18:02:34 +0200	[thread overview]
Message-ID: <4DD6909A.5040906@siemens.com> (raw)
In-Reply-To: <m3vcx8fn0f.fsf@blackfin.pond.sub.org>

On 2011-05-18 10:09, Markus Armbruster wrote:
> Jan Kiszka <jan.kiszka@siemens.com> writes:
> 
>> Include the client type name into the output of 'info network'. The
>> result looks like this:
>>
>> (qemu) info network
>> VLAN 0 devices:
>>   rtl8139.0 (NIC): model=rtl8139,macaddr=52:54:00:12:34:57
>> Devices not on any VLAN:
>>   virtio-net-pci.0 (NIC): model=virtio-net-pci,macaddr=52:54:00:12:34:56
>>    \ network1 (tap): fd=5
> 
> I guess I'd prefix vc->infostr with type=WHATEVER, for consistency with
> the command line, like this:
> 
>   (qemu) info network
>   VLAN 0 devices:
>     rtl8139.0: type=nic,model=rtl8139,macaddr=52:54:00:12:34:57
>   Devices not on any VLAN:
>     virtio-net-pci.0: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:56
>      \ network1: type=tap,fd=5

That really only creates consistency for the 'user' client. Other
clients put arbitrarily formatted strings into info_str. If it's still
preferred that way, no big deal, just wanted to point it out.

> 
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>  net.c |   18 +++++++++++++++---
>>  1 files changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/net.c b/net.c
>> index 606ce70..a4ee6b1 100644
>> --- a/net.c
>> +++ b/net.c
>> @@ -1223,6 +1223,15 @@ int do_netdev_del(Monitor *mon, const QDict *qdict, QObject **ret_data)
>>  
>>  void do_info_network(Monitor *mon)
>>  {
>> +    static const char *typename[] = {
>> +        [NET_CLIENT_TYPE_NONE]   = "none",
>> +        [NET_CLIENT_TYPE_NIC]    = "NIC",
>> +        [NET_CLIENT_TYPE_SLIRP]  = "user IPv4",
>> +        [NET_CLIENT_TYPE_TAP]    = "tap",
>> +        [NET_CLIENT_TYPE_SOCKET] = "socket",
>> +        [NET_CLIENT_TYPE_VDE]    = "VDE",
>> +        [NET_CLIENT_TYPE_DUMP]   = "dump",
>> +    };
> 
> Why not use the type names from net_client_types[]?  Easier, and
> consistent with the command line.

Will do.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-05-20 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 17:05 [Qemu-devel] [PATCH 2/2] net: Dump client type 'info network' Jan Kiszka
2011-05-18  7:35 ` Stefan Hajnoczi
2011-05-18  8:09 ` Markus Armbruster
2011-05-20 16:02   ` Jan Kiszka [this message]
2011-05-20 16:12     ` Jan Kiszka
2011-05-20 16:19       ` [Qemu-devel] [PATCH v2 " Jan Kiszka
2011-05-23  9:28         ` Markus Armbruster
2011-05-23  9:32           ` Jan Kiszka
2011-05-23 13:14             ` Markus Armbruster
2011-05-23 14:18               ` Jan Kiszka
2011-05-23 15:11                 ` Markus Armbruster
2011-05-23 16:23                   ` Jan Kiszka

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=4DD6909A.5040906@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.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 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.