From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC 1/9] hostdev: introduce the infrastructure for host device model
Date: Tue, 27 Mar 2012 15:58:55 +0200 [thread overview]
Message-ID: <4F71C79F.8000505@redhat.com> (raw)
In-Reply-To: <CAEH94LiHDD=PEg9CUuyeZg8OfBOt3sqVGKffqEH=BbXN4CQnXw@mail.gmail.com>
Il 27/03/2012 13:59, Zhi Yong Wu ha scritto:
> On Tue, Mar 27, 2012 at 6:15 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 27/03/2012 11:06, Zhi Yong Wu ha scritto:
>>>>>>> +#define DEFINE_HOSTDEV_PROP_PEER(_n, _s, _f) \
>>>>>>> + DEFINE_HOSTDEV_PROP(_n, _s, _f, hostdev_prop_netdev, NetClientState*)
>>>>>
>>>>> This should be simply a link<NetDev> property.
>>> IMHO, i don't fully understand what link<NetDev> mean. What is the
>>> difference between it and Child<NetDev>. Can you elaborate this?
>>
>> link<NetDev> is a pointer to another object. child<NetDev> means that
> Where are link<NetDev> used?
The peer property needs to be one.
> what is relationship between the two objects?
A has a pointer to B.
> it represent the relation between bus object and device object?
We're talking about netdevs, bus and object does not matter here no?
> We will not convert -net to QOM, that is, we don't care -net nic.
As long as it works that's fine but...
> Moreover, -device has exposed network card info.
... this is extremely confused. Each NIC device has a NIC-type
NetClientState. If NetClientState is converted to QOM, all of its
instances should be QOM objects, including those owned by NICs.
>> 3) the network devices already support hotplug very well, so it's also
>> not too useful to do them first. Let's first do chardevs.
>
> We hope that -netdev options info can be configurated or changed
> purely via QOM, not command line.
Yes, but does it buy anything or it is just a nice exercise?
Paolo
next prev parent reply other threads:[~2012-03-27 13:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 5:40 [Qemu-devel] [RFC 0/9] QOM: qomify -netdev zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 1/9] hostdev: introduce the infrastructure for host device model zwu.kernel
2012-03-26 5:54 ` Zhi Yong Wu
2012-03-27 8:23 ` Paolo Bonzini
2012-03-27 9:06 ` Zhi Yong Wu
2012-03-27 10:15 ` Paolo Bonzini
2012-03-27 11:59 ` Zhi Yong Wu
2012-03-27 13:58 ` Paolo Bonzini [this message]
2012-03-27 14:18 ` Zhi Yong Wu
2012-03-27 14:50 ` Paolo Bonzini
2012-03-27 21:21 ` Zhi Yong Wu
2012-03-28 6:41 ` Paolo Bonzini
2012-03-28 7:50 ` Zhi Yong Wu
2012-03-28 7:53 ` Zhi Yong Wu
2012-03-28 8:02 ` Paolo Bonzini
2012-03-28 8:05 ` 陳韋任
2012-03-28 8:25 ` Zhi Yong Wu
2012-03-28 8:29 ` 陳韋任
2012-03-26 5:40 ` [Qemu-devel] [PATCH] net: qomify -netdev zwu.kernel
2012-03-26 5:40 ` zwu.kernel
2012-03-26 5:44 ` Zhi Yong Wu
2012-03-26 5:40 ` [Qemu-devel] [RFC 2/9] net: introduce one net host device class zwu.kernel
2012-03-27 8:30 ` Paolo Bonzini
2012-03-27 9:13 ` Zhi Yong Wu
2012-03-26 5:40 ` [Qemu-devel] [RFC 3/9] net: adjust net common part for qomify -netdev zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 4/9] net: adjust nic init API zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 5/9] net: adjust dump " zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 6/9] net: qomify -netdev user zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 7/9] net: qomify -netdev socket zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 8/9] net: qomify -netdev vde zwu.kernel
2012-03-26 5:40 ` [Qemu-devel] [RFC 9/9] net: qomify -netdev tap & -netdev bridge zwu.kernel
2012-03-26 11:54 ` [Qemu-devel] [RFC 0/9] QOM: qomify -netdev Stefan Hajnoczi
2012-03-26 14:20 ` Zhi Yong Wu
2012-03-27 8:19 ` Paolo Bonzini
2012-03-27 9:03 ` Zhi Yong Wu
2012-03-26 14:39 ` Andreas Färber
2012-03-26 14:57 ` Stefan Hajnoczi
2012-03-26 15:01 ` Zhi Yong Wu
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=4F71C79F.8000505@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.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.