# 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/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 a3bf9fbdad600b1e4335dd90979f8d6072e4f602 # < make -s -j 48 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- defconfig # make -s -j 48 ARCH=arm64 O=/kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:40: LSE atomics not supported by binutils /kisskb/src/net/ipv4/fib_semantics.c: In function 'fib_check_nh_v4_gw': /kisskb/src/net/ipv4/fib_semantics.c:1027:12: warning: 'err' may be used uninitialized in this function [-Wmaybe-uninitialized] if (!tbl || err) { ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr': /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] pd->msg->buf[real_pos] = data; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:372:16: note: 'data' was declared here unsigned char data; ^ In file included from /kisskb/src/include/linux/rwsem.h:16:0, from /kisskb/src/include/linux/notifier.h:15, from /kisskb/src/include/linux/clk.h:17, from /kisskb/src/drivers/tty/serial/sh-sci.c:24: /kisskb/src/drivers/tty/serial/sh-sci.c: In function 'sci_dma_rx_submit': /kisskb/src/include/linux/spinlock.h:288:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] _raw_spin_unlock_irqrestore(lock, flags); \ ^ /kisskb/src/drivers/tty/serial/sh-sci.c:1353:16: note: 'flags' was declared here unsigned long flags; ^ Completed OK # rm -rf /kisskb/build/powerpc-next_arm64-defconfig_arm64-gcc5.4 # Build took: 0:03:59.953488