On 09/11/20 18:27, Claudio Fontana wrote:
Defer the x86 models registration to MODULE_INIT_ACCEL_CPU, so that accel-specific types can be used as parent types for all cpu models. Use the generic TYPE_X86_CPU only if no accel-specific specialization is enabled.
Can we use an accel-specific ops struct, and avoid having accel-specific types? Having dynamic types like these would make it very hard to build a schema of QOM objects.
Paolo