[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 0/9] QOM: qomify -netdev
|
From: |
Zhi Yong Wu |
|
Subject: |
Re: [Qemu-devel] [RFC 0/9] QOM: qomify -netdev |
|
Date: |
Mon, 26 Mar 2012 23:01:58 +0800 |
On Mon, Mar 26, 2012 at 10:39 PM, Andreas Färber <address@hidden> wrote:
> Am 26.03.2012 13:54, schrieb Stefan Hajnoczi:
>> I think host
>> devices will also need to 2-step creation process (init and realize).
>
> Series tested and sent out today. :)
As you've known, some models are not based on DeviceState and
DeviceClass, such as CPUClass and HOSTDeviceClass.
If property structure definition and their put/set functions don't
depend on DeviceState and more generic, that will be more great.
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
Regards,
Zhi Yong Wu
- [Qemu-devel] [PATCH] net: qomify -netdev, (continued)
- [Qemu-devel] [PATCH] net: qomify -netdev, zwu . kernel, 2012/03/26
- [Qemu-devel] [RFC 7/9] net: qomify -netdev socket, zwu . kernel, 2012/03/26
- [Qemu-devel] [RFC 8/9] net: qomify -netdev vde, zwu . kernel, 2012/03/26
- [Qemu-devel] [RFC 5/9] net: adjust dump init API, zwu . kernel, 2012/03/26
- [Qemu-devel] [RFC 9/9] net: qomify -netdev tap & -netdev bridge, zwu . kernel, 2012/03/26
- Re: [Qemu-devel] [RFC 0/9] QOM: qomify -netdev, Stefan Hajnoczi, 2012/03/26