Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp806020imi; Fri, 22 Jul 2022 09:52:10 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s/9+hQq7PzfdL2+AtRhe16RdWMjC30P1wzl+PeNkyLwqa6nCFJqsl4rkoHrpUUPljUfpu+ X-Received: by 2002:a05:6870:32c9:b0:10d:ba23:f7b4 with SMTP id r9-20020a05687032c900b0010dba23f7b4mr502256oac.133.1658508729781; Fri, 22 Jul 2022 09:52:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658508729; cv=none; d=google.com; s=arc-20160816; b=TmlmGOOBAYZIMLa/zDu0gSZY6om97CeEmnt/84PeaITa4eDMwjT7qYXZErOtoIL1X3 ORoqzP918oqTUSCGJ6H46dbGCpE+Mi6MIeOGD8rVk10MKHabDdtgplOQKHyAqRgcIW3H w6IAXuyVXyqyIcCQ3FHF3MECcRnYYzGtFisxqvPRowJVNFIXExY+7W4Ck6OtDvMWoJho Hrfyqw0W0cYkUljb9b0MLqLe9uLfcn5j1KK756UeUE5Ma/84M67EVYGX5SgBT9MltI9U ADK855HIL4S8urmrbLWc6O96cShCB1Fn5wcnwVud8dSmDQjjywwa70tk2HPhKdOnbUR4 vk5g== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=wi3p6cYevYgSzxpRYQW2/GvJN4seuvoUHVHYEM8rd/c=; b=BSpITF1lo6Jd2VCgMorVeN4dHYEZbaAsrtTvj6f0JEgCVxDzgSQOBVY4IO7yRT08r0 5nj3DLc65pxLrpPAPPA5Xu9xZmWDPdm22jAasZhC4Z662IRyyqr9M5Z6vTC1DRi7ERFw ExXNN8kHjl63DTr/L78YQNJY3ex7P4D2KFtKiFVF/JNyhs9VQTWtFC0O0WKY7vh4zJtC ku6eFpOzajcuN+ALPS8KNBecUhHiv5hgdrrTGeU0PiQLKwoWOLb38vGYNZIYSPlKXAQx fBdC2qfo7KUHpyzwno790L8GySNQc0LDtzGN0WwrsZds+BlgKKOpwwtXfPltjAf0o/Pl 6Lrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@rivosinc-com.20210112.gappssmtp.com header.s=20210112 header.b="Zsl/HCR/"; 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 m19-20020a056808025300b0033a349b67b7si4592822oie.1.2022.07.22.09.51.54; Fri, 22 Jul 2022 09:52:09 -0700 (PDT) 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=@rivosinc-com.20210112.gappssmtp.com header.s=20210112 header.b="Zsl/HCR/"; 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 S235934AbiGVQvA (ORCPT + 99 others); Fri, 22 Jul 2022 12:51:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47432 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235645AbiGVQu5 (ORCPT ); Fri, 22 Jul 2022 12:50:57 -0400 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 305D329812 for ; Fri, 22 Jul 2022 09:50:55 -0700 (PDT) Received: by mail-pf1-x432.google.com with SMTP id d10so4907944pfd.9 for ; Fri, 22 Jul 2022 09:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20210112.gappssmtp.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=wi3p6cYevYgSzxpRYQW2/GvJN4seuvoUHVHYEM8rd/c=; b=Zsl/HCR/HfwmXiX43HZ5K1ARQTPoyE5IMqULQVKIo6SK/77BnXc56/Jwf4h3JM5WT8 TnpdDx+JdlDtjutzANTIBh8TZ339Ki0MOxYlUXsv0D9GIPmyY02caVS+RNE9mZ80OsDc 1loE+ynHVL2rTaVr1bhLzHHF2Is4dV2NVBmu2qz36cSiz9SsGUp9Yur12O5CNmfBzkOv dS94okAjOgJM5DHNwg7PC6jD0vMWNWO2Xg0LdhcePYVmkNUY7m6wH+g92iq11bvHng8T +rsVTJ2WZJuSAARtp2ah0qnYhu4/SKrE/BzJkLm+kh3VTb0Vn+2jAyQxzHlhFTJW8Pc+ F1kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=wi3p6cYevYgSzxpRYQW2/GvJN4seuvoUHVHYEM8rd/c=; b=U63T6Mlx96TFOPMKRowYjHQjQ0OqlU1SwJqdMC1w6IJ1ThjpOuszTpL24BTdqZR9Qs BMrLHGT4ncGdyWQA7lIwalnf0+34jkB/y6ihkmxI8Pgy0vtjsCqakrI896RJCl49JbQG C7nRy6H4zzsxJzzVVBPTvboLi/+GqAuoGfMZrwnY26too2xaPslcDgmkfnpVV+vBg71u qYW0I5vCFYnXQWU1r3Ulv9USd7bT4Snv+JGcy/yKPTiDCGHRsQnzqWYRbkzMpRA4Q/df UBEX3HnkVoEv8tPwiofNt7eNX9SRSdbZTnkRW2GwPLZ0fWDxHDrWzpkiZivXkDIBDQ89 Hb2Q== X-Gm-Message-State: AJIora/+iK//v3wt8duQ2NZcRpmZh3vOqQUfVIMR6fr+JkRisgOGIv1z glA4lMnV3GojlAJaHdqaYj3xEGDwG52gcQ== X-Received: by 2002:a63:1324:0:b0:419:afb2:af7b with SMTP id i36-20020a631324000000b00419afb2af7bmr542186pgl.367.1658508653963; Fri, 22 Jul 2022 09:50:53 -0700 (PDT) Received: from atishp.ba.rivosinc.com ([66.220.2.162]) by smtp.gmail.com with ESMTPSA id s7-20020a170902ea0700b0016a3f9e4865sm4028476plg.148.2022.07.22.09.50.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Jul 2022 09:50:53 -0700 (PDT) From: Atish Patra To: linux-kernel@vger.kernel.org Cc: Atish Patra , Albert Ou , Anup Patel , Atish Patra , Daniel Lezcano , Guo Ren , Heiko Stuebner , kvm-riscv@lists.infradead.org, kvm@vger.kernel.org, linux-riscv@lists.infradead.org, Palmer Dabbelt , Paolo Bonzini , Paul Walmsley , Rob Herring , Thomas Gleixner , Tsukasa OI , Wei Fu Subject: [PATCH v7 0/4] Add Sstc extension support Date: Fri, 22 Jul 2022 09:50:43 -0700 Message-Id: <20220722165047.519994-1-atishp@rivosinc.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,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 lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This series implements Sstc extension support which was ratified recently. Before the Sstc extension, an SBI call is necessary to generate timer interrupts as only M-mode have access to the timecompare registers. Thus, there is significant latency to generate timer interrupts at kernel. For virtualized enviornments, its even worse as the KVM handles the SBI call and uses a software timer to emulate the timecomapre register. Sstc extension solves both these problems by defining a stimecmp/vstimecmp at supervisor (host/guest) level. It allows kernel to program a timer and recieve interrupt without supervisor execution enviornment (M-mode/HS mode) intervention. KVM directly updates the vstimecmp as well if the guest kernel invokes the SBI call instead of updating stimecmp directly. This is required because KVM will enable sstc extension if the hardware supports it unless the VMM explicitly disables it for that guest. The hardware is expected to compare the vstimecmp at every cycle if sstc is enabled and any stale value in vstimecmp will lead to spurious timer interrupts. This also helps maintaining the backward compatibility with older kernels. Similary, the M-mode firmware(OpenSBI) uses stimecmp for older kernel without sstc support as STIP bit in mip is read only for hardware with sstc. The PATCH 1 & 2 enables the basic infrastructure around Sstc extension while PATCH 3 lets kernel use the Sstc extension if it is available in hardware. PATCH 4 implements the Sstc extension in KVM. This series has been tested on Qemu(RV32 & RV64) with additional patches in Qemu[2]. This series can also be found at [3]. Changes from v6->v7: 1. Fixed a compilation error reported by 0-day bot. Changes from v5->v6: 1. Moved SSTC extension enum below SVPBMT. Changes from v4->v5: 1. Added RB tag. 2. Changed the pr-format. 3. Rebased on 5.19-rc7 and kvm-queue. 4. Moved the henvcfg modification from hardware enable to vcpu_load. Changes from v3->v4: 1. Rebased on 5.18-rc6 2. Unified vstimemp & next_cycles. 3. Addressed comments in PATCH 3 & 4. Changes from v2->v3: 1. Dropped unrelated KVM fixes from this series. 2. Rebased on 5.18-rc3. Changes from v1->v2: 1. Separate the static key from kvm usage 2. Makde the sstc specific static key local to the driver/clocksource 3. Moved the vstimecmp update code to the vcpu_timer 4. Used function pointers instead of static key to invoke vstimecmp vs hrtimer at the run time. This will help in future for migration of vms from/to sstc enabled hardware to non-sstc enabled hardware. 5. Unified the vstimer & timer to 1 timer as only one of them will be used at runtime. [1] https://drive.google.com/file/d/1m84Re2yK8m_vbW7TspvevCDR82MOBaSX/view [2] https://github.com/atishp04/qemu/tree/sstc_v6 [3] https://github.com/atishp04/linux/tree/sstc_v7 Atish Patra (4): RISC-V: Add SSTC extension CSR details RISC-V: Enable sstc extension parsing from DT RISC-V: Prefer sstc extension if available RISC-V: KVM: Support sstc extension arch/riscv/include/asm/csr.h | 5 + arch/riscv/include/asm/hwcap.h | 1 + arch/riscv/include/asm/kvm_vcpu_timer.h | 7 ++ arch/riscv/include/uapi/asm/kvm.h | 1 + arch/riscv/kernel/cpu.c | 1 + arch/riscv/kernel/cpufeature.c | 1 + arch/riscv/kvm/vcpu.c | 8 +- arch/riscv/kvm/vcpu_timer.c | 144 +++++++++++++++++++++++- drivers/clocksource/timer-riscv.c | 25 +++- 9 files changed, 185 insertions(+), 8 deletions(-) -- 2.25.1