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 v2 2/2] net: Dump client type 'info network'
Date: Mon, 23 May 2011 11:32:38 +0200 [thread overview]
Message-ID: <4DDA29B6.2010204@siemens.com> (raw)
In-Reply-To: <m3k4dhbwav.fsf@blackfin.pond.sub.org>
On 2011-05-23 11:28, 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: 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
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Changes in v2:
>> - format type as "type=name"
>> - use standard type names
>> - factor out print_net_client
>>
>> net.c | 25 ++++++++++++++++++++++---
>> 1 files changed, 22 insertions(+), 3 deletions(-)
>>
>> diff --git a/net.c b/net.c
>> index 606ce70..6d06eb7 100644
>> --- a/net.c
>> +++ b/net.c
>> @@ -1221,6 +1221,22 @@ int do_netdev_del(Monitor *mon, const QDict *qdict, QObject **ret_data)
>> return 0;
>> }
>>
>> +static void print_net_client(Monitor *mon, VLANClientState *vc)
>> +{
>> + static const char *typename[] = {
>> + [NET_CLIENT_TYPE_NONE] = "none",
>> + [NET_CLIENT_TYPE_NIC] = "nic",
>> + [NET_CLIENT_TYPE_SLIRP] = "user",
>> + [NET_CLIENT_TYPE_TAP] = "tap",
>> + [NET_CLIENT_TYPE_SOCKET] = "socket",
>> + [NET_CLIENT_TYPE_VDE] = "vde",
>> + [NET_CLIENT_TYPE_DUMP] = "dump",
>> + };
>> +
>> + monitor_printf(mon, "%s: type=%s,%s\n", vc->name,
>> + typename[vc->info->type], vc->info_str);
>> +}
>
> Any particular reason for using typename[vc->info->type] instead of
> net_client[types[vc->info->type].type?
Uncertainty about the sorting of that array. Is it supposed to be
aligned to NET_CLIENT_TYPE_* definitions?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-23 9:32 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
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 [this message]
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=4DDA29B6.2010204@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 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).