Received: by 2002:a05:7412:a9a2:b0:e2:908c:2ebd with SMTP id o34csp11577rdh; Wed, 25 Oct 2023 14:29:05 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGmaOIplaEFZ6jgTEQBNGSBZ1W9dJTNL/NU089rPLqFzgiXMcPsVipn2Cb8UpafysmMhDAE X-Received: by 2002:a25:b322:0:b0:d88:a049:e901 with SMTP id l34-20020a25b322000000b00d88a049e901mr14629293ybj.7.1698269345538; Wed, 25 Oct 2023 14:29:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698269345; cv=none; d=google.com; s=arc-20160816; b=f2iGyXtlM2zaTO74Q1lkgD4trtTy0a4jXonMoCvwnl5RATae0SUWfhO/rOgNYbwggh GH1ocoEVPzy5vRtmcn9vK3p0grOUO5U/qZPb9zpKGG849/oZB+ycEtOeTuwPTdC0lc3h Qj6unoxAdVlEAPoY1ltK6me63sKM/P5tnhA14sVErgLDUIWGjjQKLZXDb8KcbIAdj4Co qwXJDflyDOLWsFKyNtiTvf8CqnEBO4Di6B/DMz74D+atQIBoIavsfID+pTp4sRkI3VVK 7L2OM/d4w63hmMX1xMiBm0hVnJ85fs/FjfJz638hEBrZ3QzX9VteCEW1ta/0SZD83lFa hyrg== 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=CHFdWMwG0XVuYrxA+jwJ42IxuazTn1f6p7yKyhmvV24=; fh=MIA4D55LmeY5CfoKljFf87hWtch38CKxgXWk7Mv5Fvo=; b=emcYzlqE2TRtdSGQFfmnrWITj/sRE8bneLOiRob6nHXRM1I9evf9/nuLo7Bvv6Gc7v 5uO4Sv1qnj3F2QCNVqzb7+67LYb7ywUxqisll1rVE2p96QHDgMp7balnaRuN4GnQLUDU TZuVycmmELvxYhLNP3tUK8QMcRurkCCGUJ+qfKRwwUI2SEKAObVKIzl9qurxc+ik3Dvw VRe7zwbWzTbCHh3IhrsnAKBU+XLXBXz7ouYHblei6TIGeggxQImQ7m4xWG+vpurPyRDN MAtECQ1WvUVOeUL0akqfS0xnBjMjFhXNWUPDUfkBHxh0YKBuzqAZ+mS8I6LTwVZaMUVI 96PA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=3lO5enIH; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 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 pete.vger.email (pete.vger.email. [2620:137:e000::3:6]) by mx.google.com with ESMTPS id x13-20020a25ce0d000000b00da0338f794fsi6173894ybe.465.2023.10.25.14.29.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Oct 2023 14:29:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=3lO5enIH; dkim=neutral (no key) header.i=@linutronix.de header.s=2020e; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 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 pete.vger.email (Postfix) with ESMTP id B4A518181BB0; Wed, 25 Oct 2023 14:29:02 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at pete.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229881AbjJYV2z (ORCPT + 99 others); Wed, 25 Oct 2023 17:28:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54924 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230416AbjJYV2x (ORCPT ); Wed, 25 Oct 2023 17:28:53 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 541CF13A for ; Wed, 25 Oct 2023 14:28:51 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1698269329; 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=CHFdWMwG0XVuYrxA+jwJ42IxuazTn1f6p7yKyhmvV24=; b=3lO5enIHh8k7pYmLbb0kY3fdO8UO2uTxi2yln4VPdF/8yfLHarDilrkmpMHraOYDMluPzt uyoV+762mykRmE8+ujAK5GXAZEBvXkY/cbN9bVziCcVoucQY15DwlBW7yAyfU5VsbZG52N tPhWQ9/O0w6l3mfd5L1FjT15HmztPXZaMW0aD6tlsSsUncVb+q/VlWGXZ05l8ER0ys7Ewy Cbi6Mh2dDdRoiSWdnbgWkyb1ErOOAj10P7CP/UMVCBCNqwPfZHE9wdvFUHC9bhQvCb8n6t nNMU402hLRLtP0NciTrM+zpjwiJkb7VTFpaU9x242TPz2k76z7TTQ7zjES9wBw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1698269329; 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=CHFdWMwG0XVuYrxA+jwJ42IxuazTn1f6p7yKyhmvV24=; b=TTrjR1pUB0hW+MQqaw9ASgeFw0FupXbsY1VWK9SHLasLeMqxISdb8daC54ZB9ouvV+ujdJ 7aIMRE5YqY1ck0DQ== 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: 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> <87r0lq3j2t.ffs@tglx> <2c822e13-775c-4e55-bf2f-152dbca0c910@I-love.SAKURA.ne.jp> <871qdkch0g.ffs@tglx> Date: Wed, 25 Oct 2023 23:28:49 +0200 Message-ID: <8734xy5r3i.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 pete.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 (pete.vger.email [0.0.0.0]); Wed, 25 Oct 2023 14:29:02 -0700 (PDT) On Tue, Oct 24 2023 at 23:52, Tetsuo Handa wrote: > On 2023/10/24 22:00, Thomas Gleixner wrote: >> Interesting. Can you please tell what the replacement clocksource is >> when the TSC is disabled? > > Where can I find the replacement clocksource from? /sys/kernel/devices/system/clocksource/clocksource0/active_clocksource but I already figured it out. It selects kvm_clock as fallback, but that happens way later. At that point during AP bringup timekeeping is still based on jiffies. So that TSC unstable marking is not an issue vs. timekeeping. I have no idea what the kernel, VirtualPox or Windoze are doing during that time. I fear you need to add some debug on your own or if VirtualPox has a monitor/debugger you might use that to inspect what the guest is doing. Thanks, tglx