Re: [RFC v1 09/10] i386: split cpu.c and defer x86 models registration

[Paolo Bonzini]

On 10/11/20 11:04, Daniel P. Berrangé wrote:
> ie, we should have one class hierarchy for CPU model definitions, and
> one class hierarchy  for accelerator CPU implementations.
>
> So at runtime we then get two object instances - a CPU implementation
> and a CPU definition. The CPU implementation object should have a
> property which is a link to the desired CPU definition.

It doesn't even have to be two object instances.  The implementation can 
be nothing more than a set of function pointers.

Paolo