From: Gerd Hoffmann <kraxel@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: [Qemu-devel] Re: [PATCH 2/7] qdev: add "net-client" property
Date: Mon, 16 Nov 2009 10:03:13 +0100 [thread overview]
Message-ID: <4B011551.2070604@redhat.com> (raw)
In-Reply-To: <1258057742-18699-3-git-send-email-markmc@redhat.com>
On 11/12/09 21:28, Mark McLoughlin wrote:
> Rather than having each NIC create it's own client, let's create the
> client early and pass it down to the NIC.
'-device $nic,net-client=$name' doesn't work ...
> One advantage is that we can add parameters which only the client
> knows about, without having the NIC know anything about it - e.g. NICs
> shouldn't know about netdev vs. vlan.
What this is needed for?
> Another advantage is that we can easily get the client associated with
> a qdev.
Looks like this is the *real* reason ...
cheers,
Gerd
next prev parent reply other threads:[~2009-11-16 9:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 20:28 [Qemu-devel] [RFC PATCH 0/7] Fix qemu_announce_self() properly Mark McLoughlin
2009-11-12 20:28 ` [Qemu-devel] [PATCH 1/7] net: remove NICInfo::vc Mark McLoughlin
2009-11-12 20:28 ` [Qemu-devel] [PATCH 2/7] qdev: add "net-client" property Mark McLoughlin
2009-11-16 9:03 ` Gerd Hoffmann [this message]
2009-11-12 20:28 ` [Qemu-devel] [PATCH 3/7] net: create the VLANClientState for NICs early Mark McLoughlin
2009-11-16 9:26 ` [Qemu-devel] " Gerd Hoffmann
2009-11-12 20:28 ` [Qemu-devel] [PATCH 4/7] net: kill off NICInfo/NICConf::vlan/netdev Mark McLoughlin
2009-11-12 20:29 ` [Qemu-devel] [PATCH 5/7] qdev: add qdev_foreach() Mark McLoughlin
2009-11-16 9:28 ` [Qemu-devel] " Gerd Hoffmann
2009-11-20 14:20 ` Mark McLoughlin
2009-11-23 9:55 ` Gerd Hoffmann
2009-11-12 20:29 ` [Qemu-devel] [PATCH 6/7] qdev: add qdev_prop_get_{macaddr, net_client}() Mark McLoughlin
2009-11-12 20:29 ` [Qemu-devel] [PATCH 7/7] net: fix qemu_announce_self() Mark McLoughlin
2009-11-13 7:41 ` Mark McLoughlin
2009-11-13 8:14 ` Markus Armbruster
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=4B011551.2070604@redhat.com \
--to=kraxel@redhat.com \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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.