On Mon, 10 Feb 2014 01:23:37 +0100
Andreas Färber wrote:
> Am 31.01.2014 19:13, schrieb Eduardo Habkost:
> > Register separate QOM classes for each x86 CPU model.
> >
> > This will allow management code to more easily probe what each CPU model
> > provides, by simply creating objects using the a
On Mon, Feb 10, 2014 at 06:19:58AM -0200, Eduardo Habkost wrote:
> On Mon, Feb 10, 2014 at 01:23:37AM +0100, Andreas Färber wrote:
> [...]
> > > /**
> > > * X86CPUClass:
> > > * @parent_realize: The parent class' realize handler.
> > > @@ -49,6 +52,16 @@ typedef struct X86CPUClass {
> > >
On Mon, Feb 10, 2014 at 01:23:37AM +0100, Andreas Färber wrote:
[...]
> > /**
> > * X86CPUClass:
> > * @parent_realize: The parent class' realize handler.
> > @@ -49,6 +52,16 @@ typedef struct X86CPUClass {
> > CPUClass parent_class;
> > /*< public >*/
> >
> > +/* CPU model def
Am 31.01.2014 19:13, schrieb Eduardo Habkost:
> Register separate QOM classes for each x86 CPU model.
>
> This will allow management code to more easily probe what each CPU model
> provides, by simply creating objects using the appropriate class name,
> without having to restart QEMU.
>
> This al
Register separate QOM classes for each x86 CPU model.
This will allow management code to more easily probe what each CPU model
provides, by simply creating objects using the appropriate class name,
without having to restart QEMU.
This also allows us to eliminate the qdev_prop_set_globals_for_type
