Buildresult: powerpc-fixes/mpc86xx_defconfig/powerpc-gcc5 built on Nov 6, 17:44

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Nov 6, 17:44
Duration:	0:01:09.984558
Builder:	ka4
Revision:	KVM: PPC: Book3S HV: Mask off LPCR_MER for a vCPU before running it to avoid spurious interrupts (`a373830f96db288a3eb43a8692b6bcd0bd88dfe1)`
Target:	powerpc-fixes/mpc86xx_defconfig/powerpc-gcc5
Branch:	powerpc-fixes
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	mpc86xx_defconfig (download)
Log:	Download original Possible warnings (11) arch/powerpc/boot/dts/fsl/mvme7100.dts:135.22-137.4: Warning (pci_bridge): /pcie@f1008000: missing ranges for PCI bridge (or not a bridge) arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:102.9-116.4: Warning (pci_bridge): /pcie@f1008000/pcie@0: missing ranges for PCI bridge (or not a bridge) arch/powerpc/boot/dts/fsl/mvme7100.dts:139.22-141.4: Warning (pci_bridge): /pcie@f1009000: missing ranges for PCI bridge (or not a bridge) arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:129.9-143.4: Warning (pci_bridge): /pcie@f1009000/pcie@0: missing ranges for PCI bridge (or not a bridge) arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (unit_address_format): Failed prerequisite 'pci_bridge' arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (pci_device_reg): Failed prerequisite 'pci_bridge' arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge' arch/powerpc/boot/dts/fsl/mvme7100.dts:30.11-32.6: Warning (i2c_bus_reg): /soc@f1000000/i2c@3000/rtc@68: missing or empty reg property arch/powerpc/boot/dts/fsl/mvme7100.dts:135.22-137.4: Warning (interrupt_provider): /pcie@f1008000: '#interrupt-cells' found, but node is not an interrupt provider arch/powerpc/boot/dts/fsl/mvme7100.dts:139.22-141.4: Warning (interrupt_provider): /pcie@f1009000: '#interrupt-cells' found, but node is not an interrupt provider arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider' Full Log # git rev-parse -q --verify a373830f96db288a3eb43a8692b6bcd0bd88dfe1^{commit} a373830f96db288a3eb43a8692b6bcd0bd88dfe1 already have revision, skipping fetch # git checkout -q -f -B kisskb a373830f96db288a3eb43a8692b6bcd0bd88dfe1 # git clean -qxdf # < git log -1 # commit a373830f96db288a3eb43a8692b6bcd0bd88dfe1 # Author: Gautam Menghani <gautam@linux.ibm.com> # Date: Mon Oct 28 14:34:09 2024 +0530 # # KVM: PPC: Book3S HV: Mask off LPCR_MER for a vCPU before running it to avoid spurious interrupts # # Running a L2 vCPU (see [1] for terminology) with LPCR_MER bit set and no # pending interrupts results in that L2 vCPU getting an infinite flood of # spurious interrupts. The 'if check' in kvmhv_run_single_vcpu() sets the # LPCR_MER bit if there are pending interrupts. # # The spurious flood problem can be observed in 2 cases: # 1. Crashing the guest while interrupt heavy workload is running # a. Start a L2 guest and run an interrupt heavy workload (eg: ipistorm) # b. While the workload is running, crash the guest (make sure kdump # is configured) # c. Any one of the vCPUs of the guest will start getting an infinite # flood of spurious interrupts. # # 2. Running LTP stress tests in multiple guests at the same time # a. Start 4 L2 guests. # b. Start running LTP stress tests on all 4 guests at same time. # c. In some time, any one/more of the vCPUs of any of the guests will # start getting an infinite flood of spurious interrupts. # # The root cause of both the above issues is the same: # 1. A NMI is sent to a running vCPU that has LPCR_MER bit set. # 2. In the NMI path, all registers are refreshed, i.e, H_GUEST_GET_STATE # is called for all the registers. # 3. When H_GUEST_GET_STATE is called for LPCR, the vcpu->arch.vcore->lpcr # of that vCPU at L1 level gets updated with LPCR_MER set to 1, and this # new value is always used whenever that vCPU runs, regardless of whether # there was a pending interrupt. # 4. Since LPCR_MER is set, the vCPU in L2 always jumps to the external # interrupt handler, and this cycle never ends. # # Fix the spurious flood by masking off the LPCR_MER bit before running a # L2 vCPU to ensure that it is not set if there are no pending interrupts. # # [1] Terminology: # 1. L0 : PAPR hypervisor running in HV mode # 2. L1 : Linux guest (logical partition) running on top of L0 # 3. L2 : KVM guest running on top of L1 # # Fixes: ec0f6639fa88 ("KVM: PPC: Book3S HV nestedv2: Ensure LPCR_MER bit is passed to the L0") # Cc: stable@vger.kernel.org # v6.8+ # Signed-off-by: Gautam Menghani <gautam@linux.ibm.com> # Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com> # < /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 a373830f96db288a3eb43a8692b6bcd0bd88dfe1 # make -s -j 40 ARCH=powerpc O=/kisskb/build/powerpc-fixes_mpc86xx_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- mpc86xx_defconfig Using /kisskb/src/arch/powerpc/configs/mpc86xx_base.config as base Merging /kisskb/src/arch/powerpc/configs/86xx-hw.config Merging /kisskb/src/arch/powerpc/configs/fsl-emb-nonhw.config # # merged configuration written to .config (needs make) # # < make -s -j 40 ARCH=powerpc O=/kisskb/build/powerpc-fixes_mpc86xx_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- help # make -s -j 40 ARCH=powerpc O=/kisskb/build/powerpc-fixes_mpc86xx_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- olddefconfig # make -s -j 40 ARCH=powerpc O=/kisskb/build/powerpc-fixes_mpc86xx_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- /kisskb/src/arch/powerpc/boot/dts/fsl/mvme7100.dts:135.22-137.4: Warning (pci_bridge): /pcie@f1008000: missing ranges for PCI bridge (or not a bridge) also defined at /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:92.7-117.3 /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:102.9-116.4: Warning (pci_bridge): /pcie@f1008000/pcie@0: missing ranges for PCI bridge (or not a bridge) /kisskb/src/arch/powerpc/boot/dts/fsl/mvme7100.dts:139.22-141.4: Warning (pci_bridge): /pcie@f1009000: missing ranges for PCI bridge (or not a bridge) also defined at /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:119.7-144.3 /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:129.9-143.4: Warning (pci_bridge): /pcie@f1009000/pcie@0: missing ranges for PCI bridge (or not a bridge) arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (unit_address_format): Failed prerequisite 'pci_bridge' arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (pci_device_reg): Failed prerequisite 'pci_bridge' arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (pci_device_bus_num): Failed prerequisite 'pci_bridge' /kisskb/src/arch/powerpc/boot/dts/fsl/mvme7100.dts:30.11-32.6: Warning (i2c_bus_reg): /soc@f1000000/i2c@3000/rtc@68: missing or empty reg property /kisskb/src/arch/powerpc/boot/dts/fsl/mvme7100.dts:135.22-137.4: Warning (interrupt_provider): /pcie@f1008000: '#interrupt-cells' found, but node is not an interrupt provider also defined at /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:92.7-117.3 /kisskb/src/arch/powerpc/boot/dts/fsl/mvme7100.dts:139.22-141.4: Warning (interrupt_provider): /pcie@f1009000: '#interrupt-cells' found, but node is not an interrupt provider also defined at /kisskb/src/arch/powerpc/boot/dts/fsl/mpc8641si-post.dtsi:119.7-144.3 arch/powerpc/boot/dts/fsl/mvme7100.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider' Completed OK # rm -rf /kisskb/build/powerpc-fixes_mpc86xx_defconfig_powerpc-gcc5 # Build took: 0:01:09.984558

© Michael Ellerman 2006-2018.