# git rev-parse -q --verify a3bf9fbdad600b1e4335dd90979f8d6072e4f602^{commit} a3bf9fbdad600b1e4335dd90979f8d6072e4f602 already have revision, skipping fetch # git checkout -q -f -B kisskb a3bf9fbdad600b1e4335dd90979f8d6072e4f602 # git clean -qxdf # < git log -1 # commit a3bf9fbdad600b1e4335dd90979f8d6072e4f602 # Author: Greg Kurz # Date: Wed May 15 12:05:01 2019 +0200 # # powerpc/pseries: Fix xive=off command line # # On POWER9, if the hypervisor supports XIVE exploitation mode, the # guest OS will unconditionally requests for the XIVE interrupt mode # even if XIVE was deactivated with the kernel command line xive=off. # Later on, when the spapr XIVE init code handles xive=off, it disables # XIVE and tries to fall back on the legacy mode XICS. # # This discrepency causes a kernel panic because the hypervisor is # configured to provide the XIVE interrupt mode to the guest : # # kernel BUG at arch/powerpc/sysdev/xics/xics-common.c:135! # ... # NIP xics_smp_probe+0x38/0x98 # LR xics_smp_probe+0x2c/0x98 # Call Trace: # xics_smp_probe+0x2c/0x98 (unreliable) # pSeries_smp_probe+0x40/0xa0 # smp_prepare_cpus+0x62c/0x6ec # kernel_init_freeable+0x148/0x448 # kernel_init+0x2c/0x148 # ret_from_kernel_thread+0x5c/0x68 # # Look for xive=off during prom_init and don't ask for XIVE in this # case. One exception though: if the host only supports XIVE, we still # want to boot so we ignore xive=off. # # Similarly, have the spapr XIVE init code to looking at the interrupt # mode negotiated during CAS, and ignore xive=off if the hypervisor only # supports XIVE. # # Fixes: eac1e731b59e ("powerpc/xive: guest exploitation of the XIVE interrupt controller") # Cc: stable@vger.kernel.org # v4.20 # Reported-by: Pavithra R. Prakash # Signed-off-by: Greg Kurz # Reviewed-by: Cédric Le Goater # Signed-off-by: Michael Ellerman # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version # < git log --format=%s --max-count=1 a3bf9fbdad600b1e4335dd90979f8d6072e4f602 # < make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+NO_NUMA_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- powernv_defconfig # Added to kconfig CONFIG_NUMA=n # yes \n | make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+NO_NUMA_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- oldconfig yes: standard output: Broken pipe # make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+NO_NUMA_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- /kisskb/src/kernel/futex.c: In function 'do_futex': /kisskb/src/kernel/futex.c:1658:17: warning: 'oldval' may be used uninitialized in this function [-Wmaybe-uninitialized] return oldval == cmparg; ^ /kisskb/src/kernel/futex.c:1633:6: note: 'oldval' was declared here int oldval, ret; ^ WARNING: vmlinux.o(.text+0x3128): Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:early_setup() The function start_here_multiplatform() references the function __init early_setup(). This is often because start_here_multiplatform lacks a __init annotation or the annotation of early_setup is wrong. WARNING: vmlinux.o(.text+0x3164): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel() The function start_here_common() references the function __init start_kernel(). This is often because start_here_common lacks a __init annotation or the annotation of start_kernel is wrong. Completed OK # rm -rf /kisskb/build/powerpc-next_powernv_defconfig+NO_NUMA_ppc64le-gcc5 # Build took: 0:02:40.444563