From: Stefan Hajnoczi <stefanha@gmail.com>
To: Amos Kong <akong@redhat.com>
Cc: stefanha@redhat.com, qemu-devel@nongnu.org,
anthony@codemonkey.ws, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] net: make nic name unique
Date: Fri, 12 Apr 2013 11:06:18 +0200 [thread overview]
Message-ID: <20130412090618.GF31055@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1365681519-4614-1-git-send-email-akong@redhat.com>
On Thu, Apr 11, 2013 at 07:58:39PM +0800, Amos Kong wrote:
> If we don't assign 'id' for nic device, device's name will be $model.$idx.
> The $idx is always 0 if we use new style of cmdline. This problem was
> introduced by commit d33d93b2.
>
> eg:
> # qemu-upstream -device virtio-net-pci,netdev=h1 -netdev tap,id=h1 \
> -device virtio-net-pci,netdev=h2 -netdev tap,id=h2 ..
> (qemu) info network
> virtio-net-pci.0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:56
> \ h1: index=0,type=tap,ifname=tap0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
> virtio-net-pci.0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:57
> \ h2: index=0,type=tap,ifname=tap1,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown
>
> This patch remove the check of hub, allocate increased id for all devices
> that have same model.
>
> Signed-off-by: Amos Kong <akong@redhat.com>
> ---
> net/net.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
I looked a bit more into this. Markus added NIC naming in
53e51d85ef1fdd295c8f09792b8e7490c148f4b3. Please include this commit ID
in the commit message.
My hub patches incorrectly dropped Markus' fix and I actually documented
this:
+/**
+ * Generate a name for net client
+ *
+ * Only net clients created with the legacy -net option need this.
Naming is
+ * mandatory for net clients created with -netdev.
+ */
static char *assign_name(VLANClientState *vc1, const char *model)
Please update this comment to say "Only net clients created with the legacy
-net option and NICs need this".
> diff --git a/net/net.c b/net/net.c
> index 67032f5..631e7d0 100644
> --- a/net/net.c
> +++ b/net/net.c
> @@ -171,8 +171,7 @@ static char *assign_name(NetClientState *nc1, const char *model)
> continue;
> }
> /* For compatibility only bump id for net clients on a vlan */
> - if (strcmp(nc->model, model) == 0 &&
> - net_hub_id_for_client(nc, NULL) == 0) {
> + if (strcmp(nc->model, model) == 0) {
> id++;
> }
Please delete the incorrect comment about compatibility when dropping the
net_hub_id_for_client() call.
Stefan
next prev parent reply other threads:[~2013-04-12 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 12:05 [Qemu-devel] Nic devices' name are wrongly repeated Amos Kong
2013-04-10 12:28 ` Andreas Färber
2013-04-10 14:17 ` Amos Kong
2013-04-11 8:22 ` Stefan Hajnoczi
2013-04-11 11:58 ` [Qemu-devel] [PATCH] net: make nic name unique Amos Kong
2013-04-12 9:06 ` Stefan Hajnoczi [this message]
2013-04-12 10:50 ` Markus Armbruster
2013-04-15 10:55 ` [Qemu-devel] [PATCH v2] net: make network client " Amos Kong
2013-04-18 11:25 ` Stefan Hajnoczi
2013-04-18 8:19 ` [Qemu-devel] 'id' assigned to -device could not be set as net-client name (was Re: Nic devices' name are wrongly repeated) Amos Kong
2013-04-18 9:12 ` KONRAD Frédéric
2013-04-18 9:47 ` Amos Kong
2013-04-18 10:03 ` KONRAD Frédéric
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=20130412090618.GF31055@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).