[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 0/8] include qdev core in *-user, make CPU child o
From: |
Avi Kivity |
Subject: |
Re: [Qemu-devel] [RFC 0/8] include qdev core in *-user, make CPU child of DeviceState |
Date: |
Wed, 22 Aug 2012 12:05:44 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 |
On 08/21/2012 06:42 PM, Eduardo Habkost wrote:
> So, here's a third suggestion to the CPU/DeviceState problem. Basically I
> split
> the qdev code into a core (that can be easily compiled into *-user), and a
> part
> specific to qemu-system-*.
>
I'm barging in late here, so sorry if this has been suggested and shot
down: is it not possible to use composition here?
typedef ... CPU;
typedef struct CPUState {
DeviceState qdev;
CPU cpu;
} CPUState;
But I guess bringing qdev to -user is inevitable.
--
error compiling committee.c: too many arguments to function
- Re: [Qemu-devel] [RFC 4/8] cleanup error.h, included qapi-types.h aready has stdbool.h, (continued)
- [Qemu-devel] [RFC 7/8] include core qdev code into *-user, too, Eduardo Habkost, 2012/08/21
- [Qemu-devel] [RFC 3/8] qapi-types.h doesn't really need to include qemu-common.h, Eduardo Habkost, 2012/08/21
- [Qemu-devel] [RFC 2/8] qdev: split up header so it can be used in cpu.h, Eduardo Habkost, 2012/08/21
- [Qemu-devel] [RFC 5/8] split qdev into a core and code used only by qemu-system-*, Eduardo Habkost, 2012/08/21
- Re: [Qemu-devel] [RFC 0/8] include qdev core in *-user, make CPU child of DeviceState,
Avi Kivity <=