On Mon, Dec 05, 2016 at 07:13:36PM +0100, David Hildenbrand wrote:
>
> > > Is static really needed? I can understand why migration-safe might be
> > > of interest, but can't see how "static" could help (I mean we have
> > > static expansion for this purpose). Do you have anything special in
> > >
Is static really needed? I can understand why migration-safe might be
of interest, but can't see how "static" could help (I mean we have
static expansion for this purpose). Do you have anything special in
mind regarding exposing "static"?
I didn't have any specific use case in mind. My main wo
On Mon, Dec 05, 2016 at 04:15:38PM +0100, David Hildenbrand wrote:
> Am 02.12.2016 um 22:17 schrieb Eduardo Habkost:
> > This series implements query-cpu-model-expansion on target-i386.
> >
> > QAPI / interface changes
> >
> >
> > When implementing this, I have noticed th
Am 02.12.2016 um 22:17 schrieb Eduardo Habkost:
This series implements query-cpu-model-expansion on target-i386.
QAPI / interface changes
When implementing this, I have noticed that the "host" CPU model
in i386 includes some migration-unsafe features that can't be
trans
This series implements query-cpu-model-expansion on target-i386.
QAPI / interface changes
When implementing this, I have noticed that the "host" CPU model
in i386 includes some migration-unsafe features that can't be
translated to any migration-safe representation: "pmu",
