diff options
| author | Igor Mammedov | 2017-10-09 21:50:59 +0200 |
|---|---|---|
| committer | David Gibson | 2017-10-17 01:34:00 +0200 |
| commit | b8e999673bd479eed7e71a5e8bc468bca4e31d7d (patch) | |
| tree | f0a0b41845a6746c950abedc256ce069ae83a195 /scripts/modules/module_block.py | |
| parent | ppc: spapr: replace ppc_cpu_parse_features() with cpu_parse_cpu_model() (diff) | |
| download | qemu-b8e999673bd479eed7e71a5e8bc468bca4e31d7d.tar.gz qemu-b8e999673bd479eed7e71a5e8bc468bca4e31d7d.tar.xz qemu-b8e999673bd479eed7e71a5e8bc468bca4e31d7d.zip | |
ppc: move '-cpu foo,compat=xxx' parsing into ppc_cpu_parse_featurestr()
there is a dedicated callback CPUClass::parse_features
which purpose is to convert -cpu features into a set of
global properties AND deal with compat/legacy features
that couldn't be directly translated into CPU's properties.
Create ppc variant of it (ppc_cpu_parse_featurestr) and
move 'compat=val' handling from spapr_cpu_core.c into it.
That removes a dependency of board/core code on cpu_model
parsing and would let to reuse common -cpu parsing
introduced by 6063d4c0
Set "max-cpu-compat" property only if it exists, in practice
it should limit 'compat' hack to spapr machine and allow
to avoid including machine/spapr headers in target/ppc/cpu.c
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'scripts/modules/module_block.py')
0 files changed, 0 insertions, 0 deletions