[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 06c025: host-utils: Fix overflow detection in
|
From: |
Peter Maydell |
|
Subject: |
[Qemu-commits] [qemu/qemu] 06c025: host-utils: Fix overflow detection in divu128() |
|
Date: |
Thu, 30 Sep 2021 08:18:58 -0700 |
Branch: refs/heads/staging
Home: https://github.com/qemu/qemu
Commit: 06c0259a086f0f4ddd57a14ba811bba0b9e45130
https://github.com/qemu/qemu/commit/06c0259a086f0f4ddd57a14ba811bba0b9e45130
Author: Luis Pires <luis.pires@eldorado.org.br>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M util/host-utils.c
Log Message:
-----------
host-utils: Fix overflow detection in divu128()
The previous code didn't detect overflows if the high 64-bit
of the dividend were equal to the 64-bit divisor. In that case,
64 bits wouldn't be enough to hold the quotient.
Signed-off-by: Luis Pires <luis.pires@eldorado.org.br>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-Id: <20210910112624.72748-2-luis.pires@eldorado.org.br>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 4ff2a971f4dd533140c01607a0c776ba8d837bc7
https://github.com/qemu/qemu/commit/4ff2a971f4dd533140c01607a0c776ba8d837bc7
Author: Luis Pires <luis.pires@eldorado.org.br>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M include/qemu/host-utils.h
Log Message:
-----------
host-utils: fix missing zero-extension in divs128
*plow (lower 64 bits of the dividend) is passed into divs128() as
a signed 64-bit integer. When building an __int128_t from it, it
must be zero-extended, instead of sign-extended.
Suggested-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Luis Pires <luis.pires@eldorado.org.br>
Message-Id: <20210910112624.72748-3-luis.pires@eldorado.org.br>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: d03bba0bfbe6dcacc9d7be2b664d70fde081cc47
https://github.com/qemu/qemu/commit/d03bba0bfbe6dcacc9d7be2b664d70fde081cc47
Author: Luis Pires <luis.pires@eldorado.org.br>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M include/qemu/host-utils.h
Log Message:
-----------
host-utils: introduce uabs64()
Introduce uabs64(), a function that returns the absolute value of
a 64-bit int as an unsigned value. This avoids the undefined behavior
for common abs implementations, where abs of the most negative value is
undefined.
Signed-off-by: Luis Pires <luis.pires@eldorado.org.br>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20210910112624.72748-4-luis.pires@eldorado.org.br>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: bb89646c75e46db0074e263d74770dac6f0a29fc
https://github.com/qemu/qemu/commit/bb89646c75e46db0074e263d74770dac6f0a29fc
Author: Luis Pires <luis.pires@eldorado.org.br>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/i386/kvm/i8254.c
Log Message:
-----------
i386/kvm: Replace abs64() with uabs64() from host-utils
Drop abs64() and use uabs64() from host-utils, which avoids
an undefined behavior when taking abs of the most negative value.
Signed-off-by: Luis Pires <luis.pires@eldorado.org.br>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Message-Id: <20210910112624.72748-5-luis.pires@eldorado.org.br>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 3ad2111175dddb4e396c25ce242a5c7763d42631
https://github.com/qemu/qemu/commit/3ad2111175dddb4e396c25ce242a5c7763d42631
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/spapr_cpu_core.c
Log Message:
-----------
ppc/spapr: Add a POWER10 DD2 CPU
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-3-clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 40ef88ba77ac84baab3a78171a49829a6cd1d3e0
https://github.com/qemu/qemu/commit/40ef88ba77ac84baab3a78171a49829a6cd1d3e0
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/pnv_xscom.c
Log Message:
-----------
ppc/pnv: Add a comment on the "primary-topology-index" property
On P10, the chip id is calculated from the "Primary topology table
index". See skiboot commits for more information [1].
This information is extracted from the hdata on real systems which
QEMU needs to emulate. Add this property for all machines even if it
is only used on POWER10.
[1] https://github.com/open-power/skiboot/commit/2ce3f083f399
https://github.com/open-power/skiboot/commit/a2d4d7f9e14a
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-4-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 0e5e9ff455dc529ee9e3c485d4543cdcaa04ab8b
https://github.com/qemu/qemu/commit/0e5e9ff455dc529ee9e3c485d4543cdcaa04ab8b
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/pnv.c
Log Message:
-----------
ppc/pnv: Remove useless variable
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-5-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 89d2468d964e635eb80d4d00c29074a28d0e6d19
https://github.com/qemu/qemu/commit/89d2468d964e635eb80d4d00c29074a28d0e6d19
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/intc/xive.c
M include/hw/ppc/xive.h
Log Message:
-----------
ppc/xive: Export priority_to_ipb() helper
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-7-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: daf115cf9a42bb42eabaf6177e59084c22cc7b1a
https://github.com/qemu/qemu/commit/daf115cf9a42bb42eabaf6177e59084c22cc7b1a
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/intc/xive.c
M include/hw/ppc/xive.h
Log Message:
-----------
ppc/xive: Export xive_tctx_word2() helper
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-8-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 92612f1550fb11c2bda09821bad11c6349c283cf
https://github.com/qemu/qemu/commit/92612f1550fb11c2bda09821bad11c6349c283cf
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/pnv.c
M hw/ppc/pnv_core.c
M include/hw/ppc/pnv_core.h
Log Message:
-----------
ppc/pnv: Rename "id" to "quad-id" in PnvQuad
This to avoid possible conflicts with the "id" property of QOM objects.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210901094153.227671-9-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 325ba52a4e53fac6db65fcb3bd995e8e56a89eb0
https://github.com/qemu/qemu/commit/325ba52a4e53fac6db65fcb3bd995e8e56a89eb0
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M docs/system/ppc/powernv.rst
Log Message:
-----------
docs/system: ppc: Update the URL for OpenPOWER firmware images
This also fixes a small skiboot/skiroot typo and removes the links to
the specific POWER8 and POWER9 images since the firmware images can be
used to run all machines.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210902130928.528803-2-clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: f640afec1a14e99d561f7da93e3fc8a5e1206384
https://github.com/qemu/qemu/commit/f640afec1a14e99d561f7da93e3fc8a5e1206384
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/pnv.c
Log Message:
-----------
ppc/pnv: Add an assert when calculating the RAM distribution on chips
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210902130928.528803-3-clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a3d67f3e5d5bfe480eeb83d24546191b681b7c38
https://github.com/qemu/qemu/commit/a3d67f3e5d5bfe480eeb83d24546191b681b7c38
Author: Luis Pires <luis.pires@eldorado.org.br>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M target/ppc/int_helper.c
Log Message:
-----------
target/ppc: fix setting of CR flags in bcdcfsq
According to the ISA, CR should be set based on the source value, and
not on the packed decimal result.
The way this was implemented would cause GT, LT and EQ to be set
incorrectly when the source value was too large and the 31 least
significant digits of the packed decimal result ended up being all zero.
This would happen for source values of +/-10^31, +/-10^32, etc.
The new implementation fixes this and also skips the result calculation
altogether in case of src overflow.
Signed-off-by: Luis Pires <luis.pires@eldorado.org.br>
Message-Id: <20210823150235.35759-1-luis.pires@eldorado.org.br>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 99b2c0622513fc98e8ed9dac56cafb6d29240e87
https://github.com/qemu/qemu/commit/99b2c0622513fc98e8ed9dac56cafb6d29240e87
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/acpi/memory_hotplug.c
Log Message:
-----------
memory_hotplug.c: handle dev->id = NULL in acpi_memory_hotplug_write()
qapi_event_send_mem_unplug_error() deals with @device being NULL by
replacing it with an empty string ("") when emitting the event. Aside
from the fact that this behavior (qapi visitor mapping NULL pointer to
"") can be patched/changed someday, there's also the lack of utility
that the event brings to listeners, e.g. "a memory unplug error happened
somewhere".
In theory we should just avoit emitting this event at all if dev->id is
NULL, but this would be an incompatible change to existing guests.
Instead, let's make the forementioned behavior explicit: if dev->id is
NULL, pass an empty string to qapi_event_send_mem_unplug_error().
Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-2-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 44d886abab268043157b08b77147cc29bff22090
https://github.com/qemu/qemu/commit/44d886abab268043157b08b77147cc29bff22090
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/spapr.c
Log Message:
-----------
spapr.c: handle dev->id in spapr_memory_unplug_rollback()
As done in hw/acpi/memory_hotplug.c, pass an empty string if dev->id
is NULL to qapi_event_send_mem_unplug_error() to avoid relying on
a behavior that can be changed in the future.
Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-3-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 91bd95ce162cd34ba29e9f6470ecdcaaaf1d768d
https://github.com/qemu/qemu/commit/91bd95ce162cd34ba29e9f6470ecdcaaaf1d768d
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M hw/ppc/spapr_drc.c
Log Message:
-----------
spapr_drc.c: do not error_report() when drc->dev->id == NULL
The error_report() call in drc_unisolate_logical() is not considering
that drc->dev->id can be NULL, and the underlying functions error_report()
calls to do its job (vprintf(), g_strdup_printf() ...) has undefined
behavior when trying to handle "%s" with NULL arguments.
Besides, there is no utility into reporting that an unknown device was
rejected by the guest.
Acked-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-4-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a5bc19c542aa2416292b820cf22ae9afa6f25916
https://github.com/qemu/qemu/commit/a5bc19c542aa2416292b820cf22ae9afa6f25916
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-29 (Wed, 29 Sep 2021)
Changed paths:
M qapi/qdev.json
Log Message:
-----------
qapi/qdev.json: fix DEVICE_DELETED parameters doc
Clarify that @device is optional and that 'path' is the device
path from QOM.
This change follows Markus' suggestion verbatim, provided in full
context here:
https://lists.gnu.org/archive/html/qemu-devel/2021-07/msg01891.html
Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-5-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: d43f1670c7908ee4bd5911ee562053b782c63f6e
https://github.com/qemu/qemu/commit/d43f1670c7908ee4bd5911ee562053b782c63f6e
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M docs/about/deprecated.rst
M qapi/machine.json
M qapi/qdev.json
M stubs/qdev.c
Log Message:
-----------
qapi/qdev.json: add DEVICE_UNPLUG_GUEST_ERROR QAPI event
At this moment we only provide one event to report a hotunplug error,
MEM_UNPLUG_ERROR. As of Linux kernel 5.12 and QEMU 6.0.0, the pseries
machine is now able to report unplug errors for other device types, such
as CPUs.
Instead of creating a (device_type)_UNPLUG_ERROR for each new device,
create a generic DEVICE_UNPLUG_GUEST_ERROR event that can be used by all
guest side unplug errors in the future. This event has a similar API as
the existing DEVICE_DELETED event, always providing the QOM path of the
device and dev->id if there's any.
With this new generic event, MEM_UNPLUG_ERROR is now marked as deprecated.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-6-danielhb413@gmail.com>
[dwg: Correct missing ')' in stubs/qdev.c]
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 4b08cd567b54e26a0608463311418197dda83e37
https://github.com/qemu/qemu/commit/4b08cd567b54e26a0608463311418197dda83e37
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_drc.c
Log Message:
-----------
spapr: use DEVICE_UNPLUG_GUEST_ERROR to report unplug errors
Linux Kernel 5.12 is now unisolating CPU DRCs in the device_removal
error path, signalling that the hotunplug process wasn't successful.
This allow us to send a DEVICE_UNPLUG_GUEST_ERROR in drc_unisolate_logical()
to signal this error to the management layer.
We also have another error path in spapr_memory_unplug_rollback() for
configured LMB DRCs. Kernels older than 5.13 will not unisolate the LMBs
in the hotunplug error path, but it will reconfigure them. Let's send
the DEVICE_UNPLUG_GUEST_ERROR event in that code path as well to cover the
case of older kernels.
Acked-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-7-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 46f2c282c32ed0e0c9366e018b98fd58a859682e
https://github.com/qemu/qemu/commit/46f2c282c32ed0e0c9366e018b98fd58a859682e
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/acpi/memory_hotplug.c
Log Message:
-----------
memory_hotplug.c: send DEVICE_UNPLUG_GUEST_ERROR in
acpi_memory_hotplug_write()
MEM_UNPLUG_ERROR is deprecated since the introduction of
DEVICE_UNPLUG_GUEST_ERROR. Keep emitting both while the deprecation of
MEM_UNPLUG_ERROR is pending.
CC: Michael S. Tsirkin <mst@redhat.com>
CC: Igor Mammedov <imammedo@redhat.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210907004755.424931-8-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 2eb1ef73b6e661bb80f6ab7d863e2528d12c434a
https://github.com/qemu/qemu/commit/2eb1ef73b6e661bb80f6ab7d863e2528d12c434a
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M target/ppc/excp_helper.c
M target/ppc/trace-events
Log Message:
-----------
target/ppc: Convert debug to trace events (exceptions)
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210920061203.989563-2-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 7279810b67b6ea16f9b6060693a286dc6deb3036
https://github.com/qemu/qemu/commit/7279810b67b6ea16f9b6060693a286dc6deb3036
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/ppc.c
Log Message:
-----------
target/ppc: Replace debug messages by asserts for unknown IRQ pins
If an unknown pin of the IRQ controller is raised, something is very
wrong in the QEMU model. It is better to abort.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210920061203.989563-3-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 1db3632a14f44e243068bcf89bcf0739b657972b
https://github.com/qemu/qemu/commit/1db3632a14f44e243068bcf89bcf0739b657972b
Author: Matheus Ferst <matheus.ferst@eldorado.org.br>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M target/ppc/cpu.h
M target/ppc/helper_regs.c
M target/ppc/translate.c
Log Message:
-----------
target/ppc: add LPCR[HR] to DisasContext and hflags
Add a Host Radix field (hr) in DisasContext with LPCR[HR] value to allow
us to decide between Radix and HPT while validating instructions
arguments. Note that PowerISA v3.1 does not require LPCR[HR] and PATE.HR
to match if the thread is in ultravisor/hypervisor real addressing mode,
so ctx->hr may be invalid if ctx->hv and ctx->dr are set.
Signed-off-by: Matheus Ferst <matheus.ferst@eldorado.org.br>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210917114751.206845-2-matheus.ferst@eldorado.org.br>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 92fb92d3e9c67f83cbbca0e2b9ca2d88fefd6643
https://github.com/qemu/qemu/commit/92fb92d3e9c67f83cbbca0e2b9ca2d88fefd6643
Author: Matheus Ferst <matheus.ferst@eldorado.org.br>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M target/ppc/translate.c
Log Message:
-----------
target/ppc: Check privilege level based on PSR and LPCR[HR] in tlbie[l]
PowerISA v3.0B made tlbie[l] hypervisor privileged when PSR=0 and HR=1.
To allow the check at translation time, we'll use the HR bit of LPCR to
check the MMU mode instead of the PATE.HR.
Signed-off-by: Matheus Ferst <matheus.ferst@eldorado.org.br>
Message-Id: <20210917114751.206845-3-matheus.ferst@eldorado.org.br>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: d98dbe2a2bec249847e789d0cb42eb5e7e93343d
https://github.com/qemu/qemu/commit/d98dbe2a2bec249847e789d0cb42eb5e7e93343d
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa.c: split FORM1 code into helpers
The upcoming FORM2 NUMA affinity will support asymmetric NUMA topologies
and doesn't need be concerned with all the legacy support for older
pseries FORM1 guests.
We're also not going to calculate associativity domains based on numa
distance (via spapr_numa_define_associativity_domains) since the
distances will be written directly into new DT properties.
Let's split FORM1 code into its own functions to allow for easier
insertion of FORM2 logic later on.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-2-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: afa3b3c9ee8ae2c7c25c93f2d6eebe09e962cd3a
https://github.com/qemu/qemu/commit/afa3b3c9ee8ae2c7c25c93f2d6eebe09e962cd3a
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa.c: scrap 'legacy_numa' concept
When first introduced, 'legacy_numa' was a way to refer to guests that
either wouldn't be affected by associativity domain calculations, namely
the ones with only 1 NUMA node, and pre 5.2 guests that shouldn't be
affected by it because it would be an userspace change. Calling these
cases 'legacy_numa' was a convenient way to label these cases.
We're about to introduce a new NUMA affinity, FORM2, and this concept
of 'legacy_numa' is now a bit misleading because, although it is called
'legacy' it is in fact a FORM1 exclusive contraint.
This patch removes spapr_machine_using_legacy_numa() and open code the
conditions in each caller. While we're at it, move the chunk inside
spapr_numa_FORM1_affinity_init() that sets all numa_assoc_array domains
with 'node_id' to spapr_numa_define_FORM1_domains(). This chunk was
being executed if !pre_5_2_numa_associativity and num_nodes => 1, the
same conditions in which spapr_numa_define_FORM1_domains() is called
shortly after.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-3-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 3a6e4ce684e48988f9736aecc6b365609e83f8d1
https://github.com/qemu/qemu/commit/3a6e4ce684e48988f9736aecc6b365609e83f8d1
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_numa.c
M include/hw/ppc/spapr.h
Log Message:
-----------
spapr_numa.c: parametrize FORM1 macros
The next preliminary step to introduce NUMA FORM2 affinity is to make
the existing code independent of FORM1 macros and values, i.e.
MAX_DISTANCE_REF_POINTS, NUMA_ASSOC_SIZE and VCPU_ASSOC_SIZE. This patch
accomplishes that by doing the following:
- move the NUMA related macros from spapr.h to spapr_numa.c where they
are used. spapr.h gets instead a 'NUMA_NODES_MAX_NUM' macro that is used
to refer to the maximum number of NUMA nodes, including GPU nodes, that
the machine can support;
- MAX_DISTANCE_REF_POINTS and NUMA_ASSOC_SIZE are renamed to
FORM1_DIST_REF_POINTS and FORM1_NUMA_ASSOC_SIZE. These FORM1 specific
macros are used in FORM1 init functions;
- code that uses MAX_DISTANCE_REF_POINTS now retrieves the
max_dist_ref_points value using get_max_dist_ref_points().
NUMA_ASSOC_SIZE is replaced by get_numa_assoc_size() and VCPU_ASSOC_SIZE
is replaced by get_vcpu_assoc_size(). These functions are used by the
generic device tree functions and h_home_node_associativity() and will
allow them to switch between FORM1 and FORM2 without changing their core
logic.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-4-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: a165ac67c3ff8dc7065aa827de36da3785ec83fd
https://github.com/qemu/qemu/commit/a165ac67c3ff8dc7065aa827de36da3785ec83fd
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_hcall.c
M hw/ppc/spapr_numa.c
M include/hw/ppc/spapr.h
Log Message:
-----------
spapr_numa.c: rename numa_assoc_array to FORM1_assoc_array
Introducing a new NUMA affinity, FORM2, requires a new mechanism to
switch between affinity modes after CAS. Also, we want FORM2 data
structures and functions to be completely separated from the existing
FORM1 code, allowing us to avoid adding new code that inherits the
existing complexity of FORM1.
The idea of switching values used by the write_dt() functions in
spapr_numa.c was already introduced in the previous patch, and
the same approach will be used when dealing with the FORM1 and FORM2
arrays.
We can accomplish that by that by renaming the existing numa_assoc_array
to FORM1_assoc_array, which now is used exclusively to handle FORM1 affinity
data. A new helper get_associativity() is then introduced to be used by the
write_dt() functions to retrieve the current ibm,associativity array of
a given node, after considering affinity selection that might have been
done during CAS. All code that was using numa_assoc_array now needs to
retrieve the array by calling this function.
This will allow for an easier plug of FORM2 data later on.
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-5-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 5dab5abe623d97929382158b43b3fd545e8edd62
https://github.com/qemu/qemu/commit/5dab5abe623d97929382158b43b3fd545e8edd62
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_hcall.c
M hw/ppc/spapr_numa.c
M include/hw/ppc/spapr_numa.h
Log Message:
-----------
spapr: move FORM1 verifications to post CAS
FORM2 NUMA affinity is prepared to deal with empty (memory/cpu less)
NUMA nodes. This is used by the DAX KMEM driver to locate a PAPR SCM
device that has a different latency than the original NUMA node from the
regular memory. FORM2 is also able to deal with asymmetric NUMA
distances gracefully, something that our FORM1 implementation doesn't
do.
Move these FORM1 verifications to a new function and wait until after
CAS, when we're sure that we're sticking with FORM1, to enforce them.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-6-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: e0eb84d4f51f26aff6210407ec658c4b9ecbc68f
https://github.com/qemu/qemu/commit/e0eb84d4f51f26aff6210407ec658c4b9ecbc68f
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr.c
M hw/ppc/spapr_numa.c
M include/hw/ppc/spapr.h
M include/hw/ppc/spapr_ovec.h
Log Message:
-----------
spapr_numa.c: FORM2 NUMA affinity support
The main feature of FORM2 affinity support is the separation of NUMA
distances from ibm,associativity information. This allows for a more
flexible and straightforward NUMA distance assignment without relying on
complex associations between several levels of NUMA via
ibm,associativity matches. Another feature is its extensibility. This base
support contains the facilities for NUMA distance assignment, but in the
future more facilities will be added for latency, performance, bandwidth
and so on.
This patch implements the base FORM2 affinity support as follows:
- the use of FORM2 associativity is indicated by using bit 2 of byte 5
of ibm,architecture-vec-5. A FORM2 aware guest can choose to use FORM1
or FORM2 affinity. Setting both forms will default to FORM2. We're not
advertising FORM2 for pseries-6.1 and older machine versions to prevent
guest visible changes in those;
- ibm,associativity-reference-points has a new semantic. Instead of
being used to calculate distances via NUMA levels, it's now used to
indicate the primary domain index in the ibm,associativity domain of
each resource. In our case it's set to {0x4}, matching the position
where we already place logical_domain_id;
- two new RTAS DT artifacts are introduced: ibm,numa-lookup-index-table
and ibm,numa-distance-table. The index table is used to list all the
NUMA logical domains of the platform, in ascending order, and allows for
spartial NUMA configurations (although QEMU ATM doesn't support that).
ibm,numa-distance-table is an array that contains all the distances from
the first NUMA node to all other nodes, then the second NUMA node
distances to all other nodes and so on;
- get_max_dist_ref_points(), get_numa_assoc_size() and get_associativity()
now checks for OV5_FORM2_AFFINITY and returns FORM2 values if the guest
selected FORM2 affinity during CAS.
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-7-danielhb413@gmail.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 0d5ba48112daf820daddb5c952265fa23e092e69
https://github.com/qemu/qemu/commit/0d5ba48112daf820daddb5c952265fa23e092e69
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa.c: handle auto NUMA node with no distance info
numa_complete_configuration() in hw/core/numa.c always adds a NUMA node
for the pSeries machine if none was specified, but without node distance
information for the single node created.
NUMA FORM1 affinity code didn't rely on numa_state information to do its
job, but FORM2 does. As is now, this is the result of a pSeries guest
with NUMA FORM2 affinity when no NUMA nodes is specified:
$ numactl -H
available: 1 nodes (0)
node 0 cpus: 0
node 0 size: 16222 MB
node 0 free: 15681 MB
No distance information available.
This can be amended in spapr_numa_FORM2_write_rtas_tables(). We're
enforcing that the local distance (the distance to the node to itself) is
always 10. This allows for the proper creation of the NUMA distance tables,
fixing the output of 'numactl -H' in the guest:
$ numactl -H
available: 1 nodes (0)
node 0 cpus: 0
node 0 size: 16222 MB
node 0 free: 15685 MB
node distances:
node 0
0: 10
CC: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210920174947.556324-8-danielhb413@gmail.com>
Acked-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: af96d2e69227fc25f663d840527dbe2a0c592400
https://github.com/qemu/qemu/commit/af96d2e69227fc25f663d840527dbe2a0c592400
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/ppc.c
M hw/ppc/trace-events
Log Message:
-----------
target/ppc: Convert debug to trace events (decrementer and IRQ)
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210920061203.989563-4-clg@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 4d9b8ef9b5ab880d491b0c41d222b42ed83bdbfe
https://github.com/qemu/qemu/commit/4d9b8ef9b5ab880d491b0c41d222b42ed83bdbfe
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/ppc.c
Log Message:
-----------
target/ppc: Fix 64-bit decrementer
The current way the mask is built can overflow with a 64-bit decrementer.
Use sextract64() to extract the signed values and remove the logic to
handle negative values which has become useless.
Cc: Luis Fernando Fujita Pires <luis.pires@eldorado.org.br>
Fixes: a8dafa525181 ("target/ppc: Implement large decrementer support for TCG")
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210920061203.989563-5-clg@kaod.org>
Reviewed-by: Luis Pires <luis.pires@eldorado.org.br>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 457279cb49d343b2c39a9efd2b28fe0fbde71f78
https://github.com/qemu/qemu/commit/457279cb49d343b2c39a9efd2b28fe0fbde71f78
Author: Bin Meng <bmeng.cn@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/intc/openpic.c
Log Message:
-----------
hw/intc: openpic: Correct the reset value of IPIDR for FSL chipset
The reset value of IPIDR should be zero for Freescale chipset, per
the following 2 manuals I checked:
- P2020RM (https://www.nxp.com/webapp/Download?colCode=P2020RM)
- P4080RM (https://www.nxp.com/webapp/Download?colCode=P4080RM)
Currently it is set to 1, which leaves the IPI enabled on core 0
after power-on reset. Such may cause unexpected interrupt to be
delivered to core 0 if the IPI is triggered from core 0 to other
cores later.
Fixes: ffd5e9fe0276 ("openpic: Reset IRQ source private members")
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/584
Signed-off-by: Bin Meng <bin.meng@windriver.com>
Message-Id: <20210918032653.646370-1-bin.meng@windriver.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 86229b68a28a8414797dd5548f3c5284f009fb53
https://github.com/qemu/qemu/commit/86229b68a28a8414797dd5548f3c5284f009fb53
Author: Bin Meng <bmeng.cn@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/intc/openpic.c
M include/hw/ppc/openpic.h
Log Message:
-----------
hw/intc: openpic: Drop Raven related codes
There is no machine that uses Motorola MCP750 (aka Raven) model.
Drop the related codes.
While we are here, drop the mentioning of Intel GW80314 I/O
companion chip in the comments as it has been obsolete for years,
and correct a typo too.
Signed-off-by: Bin Meng <bin.meng@windriver.com>
Message-Id: <20210918032653.646370-2-bin.meng@windriver.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 06caae8af0926077338e9133dd95913aead28745
https://github.com/qemu/qemu/commit/06caae8af0926077338e9133dd95913aead28745
Author: Bin Meng <bmeng.cn@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/intc/openpic.c
M include/hw/ppc/openpic.h
Log Message:
-----------
hw/intc: openpic: Clean up the styles
Correct the multi-line comment format. No functional changes.
Signed-off-by: Bin Meng <bin.meng@windriver.com>
Message-Id: <20210918032653.646370-3-bin.meng@windriver.com>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 28d86252fc6d7ff0b48a0298014e4761d8580c70
https://github.com/qemu/qemu/commit/28d86252fc6d7ff0b48a0298014e4761d8580c70
Author: Daniel Henrique Barboza <danielhb413@gmail.com>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/ppc/spapr_numa.c
Log Message:
-----------
spapr_numa.c: fixes in spapr_numa_FORM2_write_rtas_tables()
This patch has a handful of modifications for the recent added
FORM2 support:
- to not allocate more than the necessary size in 'distance_table'.
At this moment the array is oversized due to allocating uint32_t for
all elements, when most of them fits in an uint8_t. Fix it by
changing the array to uint8_t and allocating the exact size;
- use stl_be_p() to store the uint32_t at the start of 'distance_table';
- use sizeof(uint32_t) to skip the uint32_t length when populating the
distances;
- use the NUMA_DISTANCE_MIN macro from sysemu/numa.h to avoid hardcoding
the local distance value.
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Message-Id: <20210922122852.130054-2-danielhb413@gmail.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 179abc1fcf6f74e21be02c1e4ec54776354c7136
https://github.com/qemu/qemu/commit/179abc1fcf6f74e21be02c1e4ec54776354c7136
Author: Cédric Le Goater <clg@kaod.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M hw/intc/spapr_xive_kvm.c
Log Message:
-----------
spapr/xive: Fix kvm_xive_source_reset trace event
The trace event was placed in the wrong routine. Move it under
kvmppc_xive_source_reset_one().
Fixes: 4e960974d4ee ("xive: Add trace events")
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <20210922070205.1235943-1-clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 7ddb120dbc1d03b7ad2e22449ba52b83b037dbd0
https://github.com/qemu/qemu/commit/7ddb120dbc1d03b7ad2e22449ba52b83b037dbd0
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Remove machine specific files from ppc TCG CPUs entry
Currently the PowerPC TCG CPUs entry in MAINTAINERS lists all of hw/ppc/
and include/hw/ppc. Nearly all the files in those places are related to
specific ppc machine types, rather than to the actual CPUs however. Those
machine types list their own files separately, often overlapping with this.
For greater clarity, remove these misleading entries from the TCG CPUs
stanza, leaving just hw/ppc/ppc.c and hw/ppc/ppc_booke.c which are the only
ones common to a wide range of PPC TCG cpus each.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Commit: 225060a4883f3da482905d2cb94874dafacae613
https://github.com/qemu/qemu/commit/225060a4883f3da482905d2cb94874dafacae613
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Remove David & Greg as reviewers for a number of boards
Greg and I are moving towards other areas and no longer have capacity to
act as regular reviewers for several of the secondary ppc machine types.
So, remove ourselves as reviewers for Macintosh, PReP, sam460ex and
pegasos2 in MAINTAINERS.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Acked-by: BALATON Zoltan <balaton@eik.bme.hu>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Commit: 0f514eea217beeb89593fff0c222a30fa99008ca
https://github.com/qemu/qemu/commit/0f514eea217beeb89593fff0c222a30fa99008ca
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Orphan obscure ppc platforms
There are a nunber of old embedded ppc machine types which have been little
changed and in "Odd Fixes" state for a long time. With both myself and
Greg Kurz moving toward other areas, we no longer have the capacity to
keep reviewing and maintaining even the rare patches that come in for those
platforms.
Therefore, remove our names as reviewers and mark these platforms as
orphaned.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Commit: 689d24938c9a12c0fc904f8d5e2955bb4a0717c6
https://github.com/qemu/qemu/commit/689d24938c9a12c0fc904f8d5e2955bb4a0717c6
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Remove David & Greg as reviewers/co-maintainers of powernv
With our interests moving to other areas, Greg and myself no longer have
capacity to be regular reviewers of code for the powernv machine type, let
alone co-maintainers. Additionally, not being IBM employees, we don't have
easy access to the hardware information we'd need for good review.
Therefore, remove our names as reviewers and/or co-maintainers of the
powernv machine type, and the related XIVE interrupt controller.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Acked-by: Cédric Le Goater <clg@kaod.org>
Commit: ff8cdbbd7e4bb7a7422c080c004b899214a08b3a
https://github.com/qemu/qemu/commit/ff8cdbbd7e4bb7a7422c080c004b899214a08b3a
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Add information for OpenPIC
The OpenPIC interrupt controller was once the de facto standard on ppc
machines. In qemu it's now only used on some Macintosh and the
Freescale e500 machine. It has no listed maintainer, and as far as I
know, no-one who's really familiar with it any more.
Since I'm moving away from the area, I no longer have capacity to do even
minimal maintenance of it under the auspices of the ppc targets in general.
Therefore, this patch lists the main part of openpic, and marks it as
"Odd Fixes" to be looked after by Mark Cave-Ayland who handles the
Macintosh targets. The openpic_kvm variant is only used on e500, so
add it to the files for that machine type (itself already Orphaned).
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Commit: 85d887be82905aa81b5d3d6c483ff0fa9958382b
https://github.com/qemu/qemu/commit/85d887be82905aa81b5d3d6c483ff0fa9958382b
Author: David Gibson <david@gibson.dropbear.id.au>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
Log Message:
-----------
MAINTAINERS: Demote sPAPR from "Supported" to "Maintained"
qemu/KVM on Power is no longer my primary job responsibility, nor Greg
Kurz'. I still have some time for upstream maintenance, but it's no longer
accurate to say that I'm paid to do so. Therefore, reduce sPAPR (the
"pseries" machine type) from Supported to Maintained.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Commit: fce8f7735fcea23056ff41be55e73eacbca31b5e
https://github.com/qemu/qemu/commit/fce8f7735fcea23056ff41be55e73eacbca31b5e
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2021-09-30 (Thu, 30 Sep 2021)
Changed paths:
M MAINTAINERS
M docs/about/deprecated.rst
M docs/system/ppc/powernv.rst
M hw/acpi/memory_hotplug.c
M hw/i386/kvm/i8254.c
M hw/intc/openpic.c
M hw/intc/spapr_xive_kvm.c
M hw/intc/xive.c
M hw/ppc/pnv.c
M hw/ppc/pnv_core.c
M hw/ppc/pnv_xscom.c
M hw/ppc/ppc.c
M hw/ppc/spapr.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/trace-events
M include/hw/ppc/openpic.h
M include/hw/ppc/pnv_core.h
M include/hw/ppc/spapr.h
M include/hw/ppc/spapr_numa.h
M include/hw/ppc/spapr_ovec.h
M include/hw/ppc/xive.h
M include/qemu/host-utils.h
M qapi/machine.json
M qapi/qdev.json
M stubs/qdev.c
M target/ppc/cpu.h
M target/ppc/excp_helper.c
M target/ppc/helper_regs.c
M target/ppc/int_helper.c
M target/ppc/trace-events
M target/ppc/translate.c
M util/host-utils.c
Log Message:
-----------
Merge remote-tracking branch 'remotes/dg-gitlab/tags/ppc-for-6.2-20210930'
into staging
ppc patch queue for 2021-09-30
Here's the next batch of ppc related patches for qemu-6.2. Highlights
are:
* Fixes for several TCG math instructions from the El Dorado Institute
* A number of improvements to the powernv machine type
* Support for a new DEVICE_UNPLUG_GUEST_ERROR QAPI event from Daniel
Barboza
* Support for the new FORM2 PAPR NUMA representation. This allows
more specific NUMA distances, as well as asymmetric configurations
* Fix for 64-bit decrementer (used on MicroWatt CPUs)
* Assorted fixes and cleanups
* A number of updates to MAINTAINERS
Note that the DEVICE_UNPLUG_GUEST_ERROR stuff includes changes to
files outside my normal area, but has suitable Acks.
The MAINTAINERS updates are mostly about marking minor platforms
unmaintained / orphaned, and moving some pieces away from myself and
Greg. As we move onto other projects, we're going to need to drop
more of the ppc maintainership, though we're hoping we can avoid too
abrupt a change.
# gpg: Signature made Thu 30 Sep 2021 06:42:41 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/dg-gitlab/tags/ppc-for-6.2-20210930: (44 commits)
MAINTAINERS: Demote sPAPR from "Supported" to "Maintained"
MAINTAINERS: Add information for OpenPIC
MAINTAINERS: Remove David & Greg as reviewers/co-maintainers of powernv
MAINTAINERS: Orphan obscure ppc platforms
MAINTAINERS: Remove David & Greg as reviewers for a number of boards
MAINTAINERS: Remove machine specific files from ppc TCG CPUs entry
spapr/xive: Fix kvm_xive_source_reset trace event
spapr_numa.c: fixes in spapr_numa_FORM2_write_rtas_tables()
hw/intc: openpic: Clean up the styles
hw/intc: openpic: Drop Raven related codes
hw/intc: openpic: Correct the reset value of IPIDR for FSL chipset
target/ppc: Fix 64-bit decrementer
target/ppc: Convert debug to trace events (decrementer and IRQ)
spapr_numa.c: handle auto NUMA node with no distance info
spapr_numa.c: FORM2 NUMA affinity support
spapr: move FORM1 verifications to post CAS
spapr_numa.c: rename numa_assoc_array to FORM1_assoc_array
spapr_numa.c: parametrize FORM1 macros
spapr_numa.c: scrap 'legacy_numa' concept
spapr_numa.c: split FORM1 code into helpers
...
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Compare: https://github.com/qemu/qemu/compare/98850d84f754...fce8f7735fce
- [Qemu-commits] [qemu/qemu] 06c025: host-utils: Fix overflow detection in divu128(),
Peter Maydell <=