diff options
author | Igor Mammedov | 2020-12-08 17:46:06 +0100 |
---|---|---|
committer | Paolo Bonzini | 2020-12-15 18:51:53 +0100 |
commit | 55810e90cc9a5ca18289c25aa5c1e0e2dc77eadb (patch) | |
tree | 650a24a8bb0e31330874d2d68ccec0d4157dd747 /hw/arm/boot.c | |
parent | machine: introduce MachineInitPhase (diff) | |
download | qemu-55810e90cc9a5ca18289c25aa5c1e0e2dc77eadb.tar.gz qemu-55810e90cc9a5ca18289c25aa5c1e0e2dc77eadb.tar.xz qemu-55810e90cc9a5ca18289c25aa5c1e0e2dc77eadb.zip |
ppc/spapr: cleanup -machine pseries,nvdimm=X handling
Since NVDIMM support was introduced on pseries machine,
it ignored machine's nvdimm=on|off option and effectively
was always enabled on machines that support NVDIMM.
Later on commit
(28f5a716212 ppc/spapr_nvdimm: do not enable support with 'nvdimm=off')
makes QEMU error out in case user explicitly set 'nvdimm=off'
on CLI by peeking at machine_opts.
However that's a workaround and leaves 'nvdimms_state->is_enabled'
in inconsistent state (false) when it should be set true
by default.
Instead of using on machine_opts, set default to true for pseries
machine in initfn time. If user sets manually 'nvdimm=off'
it will overwrite default value to false and QEMU will error
as expected without need to peek into machine_opts.
That way pseries will have, nvdimm enabled by default and
will honor user provided 'nvdimm=on|off'.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Message-Id: <20201208164606.4109134-1-imammedo@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'hw/arm/boot.c')
0 files changed, 0 insertions, 0 deletions