Received: by 2002:a05:7412:f690:b0:e2:908c:2ebd with SMTP id ej16csp303729rdb; Thu, 19 Oct 2023 05:14:46 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGTEJ2fn7Sdihdm0xCqHUfZDZWNXr7aSgz+lEsVwUkkcb3CzHntpc0OO9v4UhEueRAN4phj X-Received: by 2002:a05:6870:1304:b0:1e9:94c1:917a with SMTP id 4-20020a056870130400b001e994c1917amr1992665oab.54.1697717685703; Thu, 19 Oct 2023 05:14:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697717685; cv=none; d=google.com; s=arc-20160816; b=CrGAL/0hg3F9EYJC9Nkq5GjzgCIZw41WRGs5HhhBnQrRRfluaO987FsHxYraYFWMtB WLiZE2nJJnE3f5xnyojyM3gPD1BxSWmN7M7HHBeSuxcM+wzf+IzO/LFDkE74WzVvXv03 Y1xDxgtkStuyyaME8KEpYLPx6qHb6vXNk633kLNxQBZie32/SM77p9OsTpgbBC7RupOx AnZUU0rMTXDoXqFikL8b96Iknvd6/uFCvj/p/JOp/3zTwKbEl/kEvZnhBX/dZgJ1a+S8 cO8802atED8hh3Kr0KfILWUPATfSQqDfsOa601Tz+t0u7H4pAvuwyoemE3XupEFiZTx0 JiyA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=58U0eUXdd4M6jZI9lKg9MYDjXA9pyTqDZLUuXlBoJw0=; fh=MIA4D55LmeY5CfoKljFf87hWtch38CKxgXWk7Mv5Fvo=; b=waqloVfUcA2XGME40C9XIW0y0WduH/B0dUmmrbQ+aXh4AUxIK+6PcoIdTtydxnUSTT JU8WsrFZwmcyMHHaafOM18iihra21kh1Zss8W4RKveBxu61OjqdKh65AW5pqynv9G1Qb xPUXUTxyHhkpUFONWPubf62pZldCrelnc6yMiNcsTzgK2pgWnkmVKT6+FIV8wdNuWVol 70RzRqS4Wn6XWqWlsQ8jC7xGwXrPqnvCP7hnp4ybFKNH2fU/1jOQrBOGEi66f5mA8/bu O0EF8fck0YurqQq8OuoMWY1Hh5fA6G+cEbFEG53o28+eKzHo5G85YsJ3fWIXIyXLf4eq nTww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=GZoPHMjR; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=7yExDj+t; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from agentk.vger.email (agentk.vger.email. [23.128.96.32]) by mx.google.com with ESMTPS id s67-20020a635e46000000b005777bea0b6asi4281993pgb.859.2023.10.19.05.14.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Oct 2023 05:14:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=GZoPHMjR; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e header.b=7yExDj+t; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by agentk.vger.email (Postfix) with ESMTP id 7BF47819165C; Thu, 19 Oct 2023 05:14:43 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at agentk.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235337AbjJSMOj (ORCPT + 99 others); Thu, 19 Oct 2023 08:14:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233183AbjJSMOh (ORCPT ); Thu, 19 Oct 2023 08:14:37 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BDC00121 for ; Thu, 19 Oct 2023 05:14:35 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1697717674; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=58U0eUXdd4M6jZI9lKg9MYDjXA9pyTqDZLUuXlBoJw0=; b=GZoPHMjR5E4rPkZ3s/bu/sVO2VPM+SyrhdhfK0s3l70+lEDoLRAszLbTIexbIyQzyfxn4R UoI0u3s2BaXC4F6j+blqzge499LIKXwPVIhxRH2XpbXKcNerLXbsysySosH5Y9ch0Lw8j+ WQfEKTIAER9hZI37UANwWoRlLlQV8JGj9cadkke8/Y8T1kBPDMqxdFHfiEnT8UB69hyusw l6mkfJI/ATDq+UyR0o/gOI6ED6nyZ9ij5Lem95Ca2iKJEn9JmDUzTnblKFBJSpu8LYx4KJ SSHcMHkA9J9JA5cgYVzTo/ys5T2pWcL8PeR662dn1H54iTMMFwzlcHViy/3mkg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1697717674; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=58U0eUXdd4M6jZI9lKg9MYDjXA9pyTqDZLUuXlBoJw0=; b=7yExDj+tM7UeVAQmasjeeBaRpV86CZ5qFF0wxbSmY+APAlANXqp52rLMcOGCITsf3ONk3+ I5kNWwGwwfcUY+BA== To: Tetsuo Handa , paulmck@kernel.org Cc: John Stultz , Stephen Boyd , LKML , Sebastian Andrzej Siewior , x86@kernel.org, joel@joelfernandes.org Subject: Re: [PATCH] clocksource: disable irq when holding watchdog_lock. In-Reply-To: <5ef329fe-1f3b-4d81-9625-9738620f051e@I-love.SAKURA.ne.jp> References: <80ff5036-8449-44a6-ba2f-0130d3be6b57@I-love.SAKURA.ne.jp> <878r826xys.ffs@tglx> <90361195-4309-4a02-bd3f-8ee606e6d35b@I-love.SAKURA.ne.jp> <5ef329fe-1f3b-4d81-9625-9738620f051e@I-love.SAKURA.ne.jp> Date: Thu, 19 Oct 2023 14:14:34 +0200 Message-ID: <87r0lq3j2t.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on agentk.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (agentk.vger.email [0.0.0.0]); Thu, 19 Oct 2023 05:14:43 -0700 (PDT) On Thu, Oct 19 2023 at 18:30, Tetsuo Handa wrote: > On 2023/10/17 23:10, Paul E. McKenney wrote: >>> But I'm hitting something different (but might be timer/scheduler related) problem. >>> What config option would cause taking more than 2 minutes to bring up only 8 CPUs? >>> (This environment is Oracle VM VirtualBox on Windows 11 host.) >>> >> The timing is about the same in both cases. Does this happen in kernels >> built with CONFIG_PROVE_LOCKING=n? > > Disabling all options in "Lock Debugging (spinlocks, mutexes, etc...)" does not help. > >> >> Either way, what mainline or -stable version is this? > > The kernel is latest commit of upstream linux.git tree. > I'm seeing this slowdown (almost hung-up) problem for many releases, > but nobody else seems to be reporting this problem. Maybe because of this: >>> (This environment is Oracle VM VirtualBox on Windows 11 host.) > The only reliable workaround is to specify "nosmp" kernel command line option. Which makes the kernel keep TSC as clocksource because there is no synchronization problem between CPU0 and CPU0 :) What is the fallback clocksource when the TSC is discarded on SMP? From the dmesg snippets I assume it is the ACPI PMTIMER, which is I/O port based and presumably takes a VMEXIT on every read and depending on the emulation this might be slooooow. So you could boot with "nosmp clocksource=acpi_pm" on the command line and compare that against a "nosmp" boot. If my assumption is right, then on UP the ACPI PM variant won't see the massive slowdown SMP observes, but there should be still an observable difference. Thanks, tglx