Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp478427rwb; Thu, 1 Dec 2022 04:48:22 -0800 (PST) X-Google-Smtp-Source: AA0mqf789328hOsFrNdqTmhrGT3RmXFpzRBF09g/KUUgKtgzql2ufen32Ag1ebtoSqCk8DFY8OtD X-Received: by 2002:a05:6a00:2444:b0:558:991a:6671 with SMTP id d4-20020a056a00244400b00558991a6671mr47777960pfj.58.1669898902421; Thu, 01 Dec 2022 04:48:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669898902; cv=none; d=google.com; s=arc-20160816; b=OPzPUV9ZDcc4fEGYNb8c8YeIAIysIUydQoo1Pl2M42X6l5Tuo55Geffho79fyVX9WI jnVYdra0IHB6mDX0sQuh0WnkvGjcRxe0yIVD+jTk5MYcFOaAIGKwM70Gt5AH3yX08yyS mWBnfskplm+oPh5GGicsMsEXaDEsf9QRFGWRkpipYaMFQT0C1n5mpK/AruOKZAbunfc6 xY0fCcxPuBC/eMVb5xTLbrtVTDC4i68fsGvJOSGD+HV47le3fD/lVUJHWgWnQBpyI5xx dxkBABUY8I1lwMveO6jB8wZmCzVcktmlA9po04Fci2HhIfl3sW3TCY9rzhKCQ/1XlPRy z0bw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=iMerckrhZTm3FZ8D21RolrP9vW5vY1yytNXMfvZLbSs=; b=hkqAxgq0sFMcCqUtM63WFGrJLGvk4m8c8foxz+kLEHlFEdMEetRXk0EJ5QKFcXzJbM pxL+57TsTv+2gnW2Fr1zOlMppORsacBIrXpsisSwfOIIJEwWoj1PCPxQ95M59vkXu7/c j3ChSGInbWUmLpVN+W4MWh9NRXHVuKVyqjFvASip/WpNvmqrXim3r9SyDamMp7RGYTvv 9Xq9HcqGDn8DgQns4u40ACkvvz75uFPCSZYKG06ctsVeUt2aDRcUlmoLxbXyDo29B+71 /tFMOCPQZix15+tiVebsLDP8ReWdNsNkXeTUbvOjKEEjLCjPrUvUDpMzWruHc1TzYg3T FIOA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b=EW5N4fof; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m1-20020a056a00080100b0057621a30261si1724536pfk.99.2022.12.01.04.48.10; Thu, 01 Dec 2022 04:48:22 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ventanamicro.com header.s=google header.b=EW5N4fof; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231379AbiLAMkP (ORCPT + 82 others); Thu, 1 Dec 2022 07:40:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51950 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231264AbiLAMkM (ORCPT ); Thu, 1 Dec 2022 07:40:12 -0500 Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 012685AE32 for ; Thu, 1 Dec 2022 04:40:09 -0800 (PST) Received: by mail-pg1-x529.google.com with SMTP id q71so1554525pgq.8 for ; Thu, 01 Dec 2022 04:40:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ventanamicro.com; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=iMerckrhZTm3FZ8D21RolrP9vW5vY1yytNXMfvZLbSs=; b=EW5N4fofLG283DGbnT+a/zHyAd4+0YOIWw6FGWlEpchFEMUJzLqhZWhWABAWelWgmp tYxkMY+aOjTkvgYbcPfiocKATHcS4FrKB9hHvgGE0qojBUvWf549A1krIqY3kTKEkQUt qBCFDeFj/9xscbLvW3OKFoVDxvmOSMe2vsQSrPEb+sikXyxGMCzD+eyP8SiY8DP5H88C aghhCxchlMILuAzqq0/vxFOIK7KUzgwIYWlErfBS5HM012J0kQSo8C/6OCx2xlYJvQLh SkpVTk52AuEe/ntV8JBSkQ01QQRqe38fI5aNMZk7pb+mXZcYuQuzK61yGSDiGUncfFke H+sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=iMerckrhZTm3FZ8D21RolrP9vW5vY1yytNXMfvZLbSs=; b=XxXSA2R29Kj7HifXX4GXEB9Uix30IF4M5kztPPxXFPeOYzw8B9V38jmIoLHpT+KCG3 1MVR2Q8LaaeOpbXOS4MPwP6jm/PVUIa5XdwxySj6UPNRvOfpTnTajpHaz++69/ZyHpql dyJdtIHCkDK910YsgPcD9w1dIeO2eSu0u1U0uRskx8fKvzWXVAMi6yJ2c0LsXrdhjFX5 DyqjrHc+jzEPvoccXi455lDKSzQ3lRsyxISORjefXW8zE/GRwgrKqLM0CY4534MfXMZ0 l3gLYqZBzTsxiqK+DD/kOiwytH16Rfs+bjWi3knITTISdB7Y+uQNnK+IA3oICTYK73xo 7mrQ== X-Gm-Message-State: ANoB5pl3VmpR6lglPFQmnPLP5TGazuUZ3Vo0iV3GC429talOLwEOuq26 D2I3OYYkIbQB59dRRx/sNJtrow== X-Received: by 2002:a05:6a00:10cd:b0:572:5c03:f7ad with SMTP id d13-20020a056a0010cd00b005725c03f7admr67744766pfu.17.1669898409211; Thu, 01 Dec 2022 04:40:09 -0800 (PST) Received: from anup-ubuntu-vm.localdomain ([171.76.81.69]) by smtp.gmail.com with ESMTPSA id b65-20020a62cf44000000b0056f0753390csm3246981pfg.96.2022.12.01.04.40.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Dec 2022 04:40:08 -0800 (PST) From: Anup Patel To: Rob Herring , Krzysztof Kozlowski , Palmer Dabbelt , Paul Walmsley , Daniel Lezcano , Thomas Gleixner Cc: Andrew Jones , Atish Patra , Samuel Holland , Conor Dooley , Anup Patel , devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Palmer Dabbelt Subject: [PATCH v5 1/3] RISC-V: time: initialize hrtimer based broadcast clock event device Date: Thu, 1 Dec 2022 18:09:52 +0530 Message-Id: <20221201123954.1111603-2-apatel@ventanamicro.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221201123954.1111603-1-apatel@ventanamicro.com> References: <20221201123954.1111603-1-apatel@ventanamicro.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Conor Dooley Similarly to commit 022eb8ae8b5e ("ARM: 8938/1: kernel: initialize broadcast hrtimer based clock event device"), RISC-V needs to initiate hrtimer based broadcast clock event device before C3STOP can be used. Otherwise, the introduction of C3STOP for the RISC-V arch timer in commit 232ccac1bd9b ("clocksource/drivers/riscv: Events are stopped during CPU suspend") leaves us without any broadcast timer registered. This prevents the kernel from entering oneshot mode, which breaks timer behaviour, for example clock_nanosleep(). A test app that sleeps each cpu for 6, 5, 4, 3 ms respectively, HZ=250 & C3STOP enabled, the sleep times are rounded up to the next jiffy: == CPU: 1 == == CPU: 2 == == CPU: 3 == == CPU: 4 == Mean: 7.974992 Mean: 7.976534 Mean: 7.962591 Mean: 3.952179 Std Dev: 0.154374 Std Dev: 0.156082 Std Dev: 0.171018 Std Dev: 0.076193 Hi: 9.472000 Hi: 10.495000 Hi: 8.864000 Hi: 4.736000 Lo: 6.087000 Lo: 6.380000 Lo: 4.872000 Lo: 3.403000 Samples: 521 Samples: 521 Samples: 521 Samples: 521 Link: https://lore.kernel.org/linux-riscv/YzYTNQRxLr7Q9JR0@spud/ Fixes: 232ccac1bd9b ("clocksource/drivers/riscv: Events are stopped during CPU suspend") Suggested-by: Samuel Holland Signed-off-by: Conor Dooley Reviewed-by: Samuel Holland Acked-by: Palmer Dabbelt --- arch/riscv/kernel/time.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/riscv/kernel/time.c b/arch/riscv/kernel/time.c index 8217b0f67c6c..1cf21db4fcc7 100644 --- a/arch/riscv/kernel/time.c +++ b/arch/riscv/kernel/time.c @@ -5,6 +5,7 @@ */ #include +#include #include #include #include @@ -29,6 +30,8 @@ void __init time_init(void) of_clk_init(NULL); timer_probe(); + + tick_setup_hrtimer_broadcast(); } void clocksource_arch_init(struct clocksource *cs) -- 2.34.1