diff options
author | 2021-04-13 15:03:52 +0200 | |
---|---|---|
committer | 2021-04-17 10:40:51 +1000 | |
commit | e9e16917bc388846163b8566a298a291d71e44c9 (patch) | |
tree | 76d570b6aa17f0579c6076cb9d314e51f3919fcb /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | powerpc/pseries: extract host bridge from pci_bus prior to bus removal (diff) | |
download | wireguard-linux-e9e16917bc388846163b8566a298a291d71e44c9.tar.xz wireguard-linux-e9e16917bc388846163b8566a298a291d71e44c9.zip |
powerpc/xive: Use the "ibm, chip-id" property only under PowerNV
The 'chip_id' field of the XIVE CPU structure is used to choose a
target for a source located on the same chip. For that, the XIVE
driver queries the chip identifier from the "ibm,chip-id" property
and compares it to a 'src_chip' field identifying the chip of a
source. This information is only available on the PowerNV platform,
'src_chip' being assigned to XIVE_INVALID_CHIP_ID under pSeries.
The "ibm,chip-id" property is also not available on all platforms. It
was first introduced on PowerNV and later, under QEMU for pSeries/KVM.
However, the property is not part of PAPR and does not exist under
pSeries/PowerVM.
Assign 'chip_id' to XIVE_INVALID_CHIP_ID by default and let the
PowerNV platform override the value with the "ibm,chip-id" property.
Signed-off-by: Cédric Le Goater <clg@kaod.org>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210413130352.1183267-1-clg@kaod.org
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions