From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84645C7EE21 for ; Thu, 4 May 2023 09:12:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230124AbjEDJMI (ORCPT ); Thu, 4 May 2023 05:12:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229535AbjEDJMH (ORCPT ); Thu, 4 May 2023 05:12:07 -0400 Received: from desiato.infradead.org (desiato.infradead.org [IPv6:2001:8b0:10b:1:d65d:64ff:fe57:4e05]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 20AA010E7; Thu, 4 May 2023 02:12:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=desiato.20200630; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=+XiowGeHBi3CxwHF5ZdOenhB+wtm31xKafLO2m4lWL4=; b=f7bdUPT10Dg0eNirxR5Yxe30BG 9W2bfOe7WTHcxriutaDO5s2eWOgxGJAkQIb2KRgJ/Qe/0n8KVrrlNDmMUaNraEg/2U0tz350SJrqF k8B3RITcOPs3o6qdkUJaz0Xpd/LqkbaWOo2nVD+eL/pxFDPFOSmiXaezoIgOVxjLZFh1xm7Fd2Ort necYA+D4v9Pydk3FbcMKKy/mhT08sFUWmiKnbt/J6DTQXAZNCr5Y7qecrI7n5PbmVwecWGagTDOqT h9xU/DkCMSYKEq7nCgHICFUoO57agQ1CC1aYJJ77dBwQVFIhup3ZkXJ0cSdTuQO8VNZpDRei4kWYG xVw8cjyA==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by desiato.infradead.org with esmtpsa (Exim 4.96 #2 (Red Hat Linux)) id 1puUzl-001hL9-0h; Thu, 04 May 2023 09:11:26 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id E0BAA3002A3; Thu, 4 May 2023 11:11:23 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id C52AB241D422C; Thu, 4 May 2023 11:11:23 +0200 (CEST) Date: Thu, 4 May 2023 11:11:23 +0200 From: Peter Zijlstra To: kernel test robot Cc: kan.liang@linux.intel.com, oe-lkp@lists.linux.dev, lkp@intel.com, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, eranian@google.com, ak@linux.intel.com Subject: Re: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update Message-ID: <20230504091123.GJ1734100@hirez.programming.kicks-ass.net> References: <20230421184529.3320912-2-kan.liang@linux.intel.com> <202304251457.d108dbb3-yujie.liu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202304251457.d108dbb3-yujie.liu@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 25, 2023 at 03:16:29PM +0800, kernel test robot wrote: > Hello, > > kernel test robot noticed "Kernel_panic-not_syncing:Timeout:Not_all_CPUs_entered_broadcast_exception_handler" on: > > commit: a17c97370d1fb9b2eac75c85136a1f70ec44eded ("[PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update") > url: https://github.com/intel-lab-lkp/linux/commits/kan-liang-linux-intel-com/perf-x86-intel-ds-Delay-the-threshold-update/20230422-024743 > base: https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git 15def34e2635ab7e0e96f1bc32e1b69609f14942 > patch link: https://lore.kernel.org/all/20230421184529.3320912-2-kan.liang@linux.intel.com/ > patch subject: [PATCH V4 2/2] perf/x86/intel/ds: Delay the threshold update > > in testcase: kvm-unit-tests-qemu > > compiler: gcc-11 > test machine: 224 threads 2 sockets Intel(R) Xeon(R) Platinum 8480+ (Sapphire Rapids) with 256G memory > > (please refer to attached dmesg/kmsg for entire log/backtrace) > > > If you fix the issue, kindly add following tag > | Reported-by: kernel test robot > | Link: https://lore.kernel.org/oe-lkp/202304251457.d108dbb3-yujie.liu@intel.com > > > [ 179.997768][ T2324] 2023-04-23 15:30:10 ./run_tests.sh > ... > [ 180.442663][T20263] x86/split lock detection: #AC: qemu-system-x86/20263 took a split_lock trap at address: 0x1e3 > [ 182.372875][ T2324] I'm going to try and replicate this on my ADL which should have split_lock crud on. How does one run this kvm-unit-test stuff, inside kvm or on bare metal?