[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [RFC] Unifying Reset Functions on the QOM heirachy
From: |
Peter Crosthwaite |
Subject: |
[Qemu-devel] [RFC] Unifying Reset Functions on the QOM heirachy |
Date: |
Wed, 27 Feb 2013 14:52:33 +1000 |
Hi All,
The lastest QOM styling guidlines have mandated that instead of using
child specific init functions (E.G. SysBusDeviceClass::init), all
devices should use DeviceClass::realize or Object::init. I'm wondering
if the same policy should be applied to resets. The main offender is
CPUClass::reset. Since TYPE_CPU is now a child of TYPE_DEVICE, can we
abandon cpu reset and move it up to the device level? Ditto for any
other device abstractions that define their own reset function.
Regards,
Peter
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [RFC] Unifying Reset Functions on the QOM heirachy,
Peter Crosthwaite <=