[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] f0638a: spapr: Handle HPT allocation failure
|
From: |
Peter Maydell |
|
Subject: |
[Qemu-commits] [qemu/qemu] f0638a: spapr: Handle HPT allocation failure in nested guest |
|
Date: |
Fri, 09 Oct 2020 09:30:40 -0700 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: f0638a0b6bba455e8eaf518f23487d6ff1f59b5a
https://github.com/qemu/qemu/commit/f0638a0b6bba455e8eaf518f23487d6ff1f59b5a
Author: Fabiano Rosas <farosas@linux.ibm.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
Log Message:
-----------
spapr: Handle HPT allocation failure in nested guest
The nested KVM code does not yet support HPT guests. Calling the
KVM_CAP_PPC_ALLOC_HTAB ioctl currently leads to KVM setting the guest
as HPT and erroneously executing code in L1 that should only run in
hypervisor mode, leading to an exception in the L1 vcpu thread when it
enters the nested guest.
This can be reproduced with -machine max-cpu-compat=power8 in the L2
guest command line.
The KVM code has since been modified to fail the ioctl when running in
a nested environment so QEMU needs to be able to handle that. This
patch provides an error message informing the user about the lack of
support for HPT in nested guests.
Reported-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
Signed-off-by: Fabiano Rosas <farosas@linux.ibm.com>
Message-Id: <20200911043123.204162-1-farosas@linux.ibm.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 9c4d1497e8d44a0045d04533bb822d453639c944
https://github.com/qemu/qemu/commit/9c4d1497e8d44a0045d04533bb822d453639c944
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_cpu_core.c
Log Message:
-----------
spapr: Fix error leak in spapr_realize_vcpu()
If spapr_irq_cpu_intc_create() fails, local_err isn't propagated and
thus leaked.
Fixes: 992861fb1e4c ("error: Eliminate error_propagate() manually")
Cc: armbru@redhat.com
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-2-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 2c82e8df4d6a99c024f3955fe6a6bf94ca59ab63
https://github.com/qemu/qemu/commit/2c82e8df4d6a99c024f3955fe6a6bf94ca59ab63
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M target/ppc/compat.c
M target/ppc/cpu.h
Log Message:
-----------
ppc: Add a return value to ppc_set_compat() and ppc_set_compat_all()
As recommended in "qapi/error.h", indicate success / failure with a
return value. Since ppc_set_compat() is called from a VMState handler,
let's make it an int so that it propagates any negative errno returned
by kvmppc_set_compat(). Do the same for ppc_set_compat_all() for
consistency, even if it isn't called in a context where a negative errno
is required on failure.
This will allow to simplify error handling in the callers.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-3-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 899134eb495fe784885cb495bb38e05639cca52a
https://github.com/qemu/qemu/commit/899134eb495fe784885cb495bb38e05639cca52a
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M target/ppc/machine.c
Log Message:
-----------
ppc: Fix return value in cpu_post_load() error path
VMState handlers are supposed to return negative errno values on failure.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-4-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a3114923d4c5f0a2ccc8b4d74b3eebad3fb6ce5d
https://github.com/qemu/qemu/commit/a3114923d4c5f0a2ccc8b4d74b3eebad3fb6ce5d
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
Log Message:
-----------
spapr: Simplify error handling in callers of ppc_set_compat()
Now that ppc_set_compat() indicates success/failure with a return
value, use it and reduce error propagation overhead.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-5-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 121afbe487b7b10b9fc683be16068368e1ad0f11
https://github.com/qemu/qemu/commit/121afbe487b7b10b9fc683be16068368e1ad0f11
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_hcall.c
Log Message:
-----------
spapr: Get rid of cas_check_pvr() error reporting
The cas_check_pvr() function has two purposes:
- finding the "best" logical PVR, ie. the most recent one supported by
the guest for this CPU type
- checking if the guest supports the real PVR of this CPU type, which
is just an optional extra information to workaround the lack of
support for "compat" mode in PR KVM
This logic doesn't need error reporting, really. If we don't find a
suitable logical PVR, we return the special value 0 which is definitely
not a valid PVR. Let the caller decide on whether it should error out
or not.
This doesn't change the behavior.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-6-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 7e92da81be377a604f4ace7551ce61dd51afbbaa
https://github.com/qemu/qemu/commit/7e92da81be377a604f4ace7551ce61dd51afbbaa
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_hcall.c
Log Message:
-----------
spapr: Simplify error handling in do_client_architecture_support()
Use the return value of ppc_set_compat_all() to check failures,
which is preferred over hijacking local_err.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-7-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a9c2cdace0a9f42d4a2b1b230baab96819b79641
https://github.com/qemu/qemu/commit/a9c2cdace0a9f42d4a2b1b230baab96819b79641
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_vio.c
Log Message:
-----------
spapr: Simplify error handling in spapr_vio_busdev_realize()
Use the return value of spapr_irq_findone() and spapr_irq_claim()
to detect failures. This allows to reduce the error propagation
overhead.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-8-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 17548fe64a68e93deb25ac1d82f1585f916b59b1
https://github.com/qemu/qemu/commit/17548fe64a68e93deb25ac1d82f1585f916b59b1
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_drc.c
M hw/ppc/spapr_nvdimm.c
M hw/ppc/spapr_pci.c
M include/hw/ppc/spapr_drc.h
Log Message:
-----------
spapr: Add a return value to spapr_drc_attach()
As recommended in "qapi/error.h", return true on success and false on
failure. This allows to reduce error propagation overhead in the callers.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-9-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: ebd226d221c4ef8192fc5b148e0aece07bd302d1
https://github.com/qemu/qemu/commit/ebd226d221c4ef8192fc5b148e0aece07bd302d1
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_drc.c
Log Message:
-----------
spapr: Simplify error handling in prop_get_fdt()
Use the return value of visit_check_struct() and visit_check_list()
for error checking instead of local_err. This allows to get rid of
the error propagation overhead.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-10-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: cfdc52747390af88086094e51ddc7f8fbeea330e
https://github.com/qemu/qemu/commit/cfdc52747390af88086094e51ddc7f8fbeea330e
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_cpu_core.c
M include/hw/ppc/spapr.h
Log Message:
-----------
spapr: Add a return value to spapr_set_vcpu_id()
As recommended in "qapi/error.h", return true on success and false on
failure. This allows to reduce error propagation overhead in the callers.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-11-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a5af92e2e9377f753d3df6b2e050b3db6f64fb7d
https://github.com/qemu/qemu/commit/a5af92e2e9377f753d3df6b2e050b3db6f64fb7d
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_cpu_core.c
Log Message:
-----------
spapr: Simplify error handling in spapr_cpu_core_realize()
As recommended in "qapi/error.h", add a bool return value to
spapr_realize_vcpu() and use it in spapr_cpu_core_realize()
in order to get rid of the error propagation overhead.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-12-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 451c6905899da0cdcd23bffef93504f93fd48d5e
https://github.com/qemu/qemu/commit/451c6905899da0cdcd23bffef93504f93fd48d5e
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_nvdimm.c
M include/hw/ppc/spapr_nvdimm.h
Log Message:
-----------
spapr: Add a return value to spapr_nvdimm_validate()
As recommended in "qapi/error.h", return true on success and false on
failure. This allows to reduce error propagation overhead in the callers.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-13-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 35dce34fbc1cfa6a26f95b83f3a8949a4150412f
https://github.com/qemu/qemu/commit/35dce34fbc1cfa6a26f95b83f3a8949a4150412f
Author: Greg Kurz <groug@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_caps.c
M include/hw/ppc/spapr.h
Log Message:
-----------
spapr: Add a return value to spapr_check_pagesize()
As recommended in "qapi/error.h", return true on success and false on
failure. This allows to reduce error propagation overhead in the callers.
Signed-off-by: Greg Kurz <groug@kaod.org>
Message-Id: <20200914123505.612812-14-groug@kaod.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 83fa6e2a9fb4359208ed1a2ac74589ef0271627a
https://github.com/qemu/qemu/commit/83fa6e2a9fb4359208ed1a2ac74589ef0271627a
Author: Cédric Le Goater <clg@kaod.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/pnv.c
Log Message:
-----------
ppc/pnv: Increase max firmware size
Builds enabling GCOV can be bigger than 4MB and the limit on FSP
systems is 16MB.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20201002091440.1349326-1-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 29bfe52a5229bd457d85e1033dbfd91fe441dcf3
https://github.com/qemu/qemu/commit/29bfe52a5229bd457d85e1033dbfd91fe441dcf3
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr.c
M include/hw/ppc/spapr.h
Log Message:
-----------
spapr: add spapr_machine_using_legacy_numa() helper
The changes to come to NUMA support are all guest visible. In
theory we could just create a new 5_1 class option flag to
avoid the changes to cascade to 5.1 and under. The reality is that
these changes are only relevant if the machine has more than one
NUMA node. There is no need to change guest behavior that has
been around for years needlesly.
This new helper will be used by the next patches to determine
whether we should retain the (soon to be) legacy NUMA behavior
in the pSeries machine. The new behavior will only be exposed
if:
- machine is pseries-5.2 and newer;
- more than one NUMA node is declared in NUMA state.
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20201007172849.302240-2-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: ee6635b227491e7d487ecd868e0dbfbb0c444217
https://github.com/qemu/qemu/commit/ee6635b227491e7d487ecd868e0dbfbb0c444217
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa: forbid asymmetrical NUMA setups
The pSeries machine does not support asymmetrical NUMA
configurations. This doesn't make much of a different
since we're not using user input for pSeries NUMA setup,
but this will change in the next patches.
To avoid breaking existing setups, gate this change by
checking for legacy NUMA support.
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20201007172849.302240-3-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 491e884e3666e0af6a1eef06df496611097a060e
https://github.com/qemu/qemu/commit/491e884e3666e0af6a1eef06df496611097a060e
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa: change reference-points and maxdomain settings
This is the first guest visible change introduced in
spapr_numa.c. The previous settings of both reference-points
and maxdomains were too restrictive, but enough for the
existing associativity we're setting in the resources.
We'll change that in the following patches, populating the
associativity arrays based on user input. For those changes
to be effective, reference-points and maxdomains must be
more flexible. After this patch, we'll have 4 distinct
levels of NUMA (0x4, 0x3, 0x2, 0x1) and maxdomains will
allow for any type of configuration the user intends to
do - under the scope and limitations of PAPR itself, of
course.
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20201007172849.302240-4-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 690fbe4295d5f1eec7c0862797abd7626a965e59
https://github.com/qemu/qemu/commit/690fbe4295d5f1eec7c0862797abd7626a965e59
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa: consider user input when defining associativity
A new function called spapr_numa_define_associativity_domains()
is created to calculate the associativity domains and change
the associativity arrays considering user input. This is how
the associativity domain between two NUMA nodes A and B is
calculated:
- get the distance D between them
- get the correspondent NUMA level 'n_level' for D. This is done
via a helper called spapr_numa_get_numa_level()
- all associativity arrays were initialized with their own
numa_ids, and we're calculating the distance in node_id ascending
order, starting from node id 0 (the first node retrieved by
numa_state). This will have a cascade effect in the algorithm because
the associativity domains that node 0 defines will be carried over to
other nodes, and node 1 associativities will be carried over after
taking node 0 associativities into account, and so on. This
happens because we'll assign assoc_src as the associativity domain
of dst as well, for all NUMA levels beyond and including n_level.
The PPC kernel expects the associativity domains of the first node
(node id 0) to be always 0 [1], and this algorithm will grant that
by default.
Ultimately, all of this results in a best effort approximation for
the actual NUMA distances the user input in the command line. Given
the nature of how PAPR itself interprets NUMA distances versus the
expectations risen by how ACPI SLIT works, there might be better
algorithms but, in the end, it'll also result in another way to
approximate what the user really wanted.
To keep this commit message no longer than it already is, the next
patch will update the existing documentation in ppc-spapr-numa.rst
with more in depth details and design considerations/drawbacks.
[1]
https://lore.kernel.org/linuxppc-dev/5e8fbea3-8faf-0951-172a-b41a2138fbcf@gmail.com/
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20201007172849.302240-5-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 307e7a34dc474c050f345eeb519d957a42f10c77
https://github.com/qemu/qemu/commit/307e7a34dc474c050f345eeb519d957a42f10c77
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M docs/specs/ppc-spapr-numa.rst
Log Message:
-----------
specs/ppc-spapr-numa: update with new NUMA support
This update provides more in depth information about the
choices and drawbacks of the new NUMA support for the
spapr machine.
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20201007172849.302240-6-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 4a7c0bd9dcb08798c6f82e55b5a3423f7ee669f1
https://github.com/qemu/qemu/commit/4a7c0bd9dcb08798c6f82e55b5a3423f7ee669f1
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2020-10-09 (Fri, 09 Oct 2020)
Changed paths:
M docs/specs/ppc-spapr-numa.rst
M hw/ppc/pnv.c
M hw/ppc/spapr.c
M hw/ppc/spapr_caps.c
M hw/ppc/spapr_cpu_core.c
M hw/ppc/spapr_drc.c
M hw/ppc/spapr_hcall.c
M hw/ppc/spapr_numa.c
M hw/ppc/spapr_nvdimm.c
M hw/ppc/spapr_pci.c
M hw/ppc/spapr_vio.c
M include/hw/ppc/spapr.h
M include/hw/ppc/spapr_drc.h
M include/hw/ppc/spapr_nvdimm.h
M target/ppc/compat.c
M target/ppc/cpu.h
M target/ppc/machine.c
Log Message:
-----------
Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-5.2-20201009' into
staging
ppc patch queue 2020-10-09
Here's the next set of ppc related patches for qemu-5.2. There are
two main things here:
* Cleanups to error handling in spapr from Greg Kurz
* Improvements to NUMA handling for spapr from Daniel Barboza
There are also a handful of other bugfixes.
# gpg: Signature made Fri 09 Oct 2020 07:02:29 BST
# gpg: using RSA key 75F46586AE61A66CC44E87DC6C38CACA20D9B392
# gpg: Good signature from "David Gibson <david@gibson.dropbear.id.au>" [full]
# gpg: aka "David Gibson (Red Hat) <dgibson@redhat.com>" [full]
# gpg: aka "David Gibson (ozlabs.org) <dgibson@ozlabs.org>"
[full]
# gpg: aka "David Gibson (kernel.org) <dwg@kernel.org>"
[unknown]
# Primary key fingerprint: 75F4 6586 AE61 A66C C44E 87DC 6C38 CACA 20D9 B392
* remotes/dgibson/tags/ppc-for-5.2-20201009:
specs/ppc-spapr-numa: update with new NUMA support
spapr_numa: consider user input when defining associativity
spapr_numa: change reference-points and maxdomain settings
spapr_numa: forbid asymmetrical NUMA setups
spapr: add spapr_machine_using_legacy_numa() helper
ppc/pnv: Increase max firmware size
spapr: Add a return value to spapr_check_pagesize()
spapr: Add a return value to spapr_nvdimm_validate()
spapr: Simplify error handling in spapr_cpu_core_realize()
spapr: Add a return value to spapr_set_vcpu_id()
spapr: Simplify error handling in prop_get_fdt()
spapr: Add a return value to spapr_drc_attach()
spapr: Simplify error handling in spapr_vio_busdev_realize()
spapr: Simplify error handling in do_client_architecture_support()
spapr: Get rid of cas_check_pvr() error reporting
spapr: Simplify error handling in callers of ppc_set_compat()
ppc: Fix return value in cpu_post_load() error path
ppc: Add a return value to ppc_set_compat() and ppc_set_compat_all()
spapr: Fix error leak in spapr_realize_vcpu()
spapr: Handle HPT allocation failure in nested guest
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Compare: https://github.com/qemu/qemu/compare/e1c30c43cd0b...4a7c0bd9dcb0
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] f0638a: spapr: Handle HPT allocation failure in nested guest,
Peter Maydell <=