[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 07/12] qdev-core: isolate reset register/unregis
From: |
Andreas Färber |
Subject: |
Re: [Qemu-devel] [PATCH 07/12] qdev-core: isolate reset register/unregister code |
Date: |
Thu, 18 Oct 2012 16:51:57 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 |
Am 17.10.2012 20:32, schrieb Eduardo Habkost:
> Anyway, I am actually wondering if we really need to include the qbus
> code on *-user. Do you think *-user will eventually use BusState objects
> too, or it will use only DeviceState objects in the foreseeable future?
My understanding is that we want DeviceState as a consistent parent and
its static properties mechanisms. Most of it, including BusState, is
going to be unused. At runtime *-user only needs the TCG fields in
CPUArchState plus the name -> object mapping mechanisms of the day for
initialization.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
[Qemu-devel] [PATCH 08/12] qdev: move reset register/unregister code to qdev-system.c, Eduardo Habkost, 2012/10/16
[Qemu-devel] [PATCH 05/12] qdev-core: isolate vmstate handling into separate functions, Eduardo Habkost, 2012/10/16
[Qemu-devel] [PATCH 09/12] move qemu_irq typedef out of cpu-common.h, Eduardo Habkost, 2012/10/16
[Qemu-devel] [PATCH 12/12] qom: make CPU a child of DeviceState, Eduardo Habkost, 2012/10/16
[Qemu-devel] [PATCH 04/12] qdev: rename qdev.c to qdev-core.c, Eduardo Habkost, 2012/10/16
[Qemu-devel] [PATCH 03/12] qdev: separate core from the code used only by qemu-system-*, Eduardo Habkost, 2012/10/16