gaosong <[email protected]> writes:
> Cc: Markus
>
> hi, Markus
>
> What is the difference between CPU_MODEL_EXPANSION_TYPE_STATIC and
> CPU_MODEL_EXPANSION_TYPE_FULL?
I don't know :)
Here's the documentation:
##
# @CpuModelExpansionType:
#
# An enumeration of CPU model expansion types.
#
# @static: Expand to a static CPU model, a combination of a static
# base model name and property delta changes. As the static base
# model will never change, the expanded CPU model will be the
# same, independent of QEMU version, machine type, machine
# options, and accelerator options. Therefore, the resulting
# model can be used by tooling without having to specify a
# compatibility machine - e.g. when displaying the "host" model.
# The @static CPU models are migration-safe.
#
# @full: Expand all properties. The produced model is not guaranteed
# to be migration-safe, but allows tooling to get an insight and
# work with model details.
#
# .. note:: When a non-migration-safe CPU model is expanded in static
# mode, some features enabled by the CPU model may be omitted,
# because they can't be implemented by a static CPU model
# definition (e.g. cache info passthrough and PMU passthrough in
# x86). If you need an accurate representation of the features
# enabled by a non-migration-safe CPU model, use @full. If you
# need a static representation that will keep ABI compatibility
# even when changing QEMU version or machine-type, use @static (but
# keep in mind that some features may be omitted).
#
# Since: 2.8
##
If you have further questions, David Hildenbrand or Eduardo Habkost
(cc'ed) might be able to help.
