Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp4792511rdb; Fri, 29 Dec 2023 13:50:19 -0800 (PST) X-Google-Smtp-Source: AGHT+IHDoT/f5hJjiRdG+gru0QqaSM33xEeW/L6COsuNEkt/uytzdb5/7w1OSu7BSYDOlJHW3yEX X-Received: by 2002:a05:6808:14ca:b0:3bb:9aec:8711 with SMTP id f10-20020a05680814ca00b003bb9aec8711mr12759874oiw.54.1703886619626; Fri, 29 Dec 2023 13:50:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703886619; cv=none; d=google.com; s=arc-20160816; b=UouFusAGhkaKb31qC5Ilnk0X1D32dvmGPqnH9dmH51SG+UTW//UKzjgOisKFCXwb+h l9VMyTkrUNGRDlVPs08DsF5uoQfGaJ6jN/A63SHhQBEOQZ9tsI/sbvyN0YQaNBXwT77g MInZBk3qByk9UAlrISd1Rs3aPmcY+HoNuvhz4OXI/rukki4NDrJS+cLi5Bvgg4HZi4JN J9q9YOUyXHcpj+QZc+ZjZ+Tprtuzj7tNdxTHK8LzZ1vASY8nddqDU1XAacGBmEbO251h l/poQqtpzBz9ONdTGqZAsCZKEb+FTGyt4S/1BgaSD+JQxzDzl9T3/JKusanA3CtMf9qT M27A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=vu5q4X23PA3gtec4TspOf+EMnf830wRQIwKELSXAAlg=; fh=fI5kEua53udNTNan966nBIymbOkavhtrnrSLRiMqZpU=; b=pMrLLa3OvMjXATrUSWwuk2KDF/sRZ1fnnYk/rRQNSRWRQLOZqZpZSFskqzwBVLNh5T uGEXs1du3uhmv9cuXOH9wOMIDXu+nKqJpVl3753fK4v21XlgjN//YR6lq9RuRvF9Sb1S zPv4M1PV7ZCpDcSVzVt6mucp0qv1NVvTzGRApZtbypoxUT4eUydCoLQReQ1rpWQdIBh8 xmeowPuKoU5SqMJmN962BxkEztTTPrUbR7X90z7qsoxuxWno7XC5sE5u4kPlZ+MXoVkT HPGcI7PL+LokJYHOiy04gnTmRJeSBkbuWEkQs3I9/ngtn5iMxP4gaE5CYaVYOUV3oekP 3Wtw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@rivosinc-com.20230601.gappssmtp.com header.s=20230601 header.b=U7gLqHhi; spf=pass (google.com: domain of linux-kernel+bounces-13247-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-13247-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id a13-20020a65418d000000b005ca4098bf66si15020292pgq.637.2023.12.29.13.50.19 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 Dec 2023 13:50:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-13247-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@rivosinc-com.20230601.gappssmtp.com header.s=20230601 header.b=U7gLqHhi; spf=pass (google.com: domain of linux-kernel+bounces-13247-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-13247-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 43119281E6F for ; Fri, 29 Dec 2023 21:50:19 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D7B6314AAE; Fri, 29 Dec 2023 21:50:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=rivosinc-com.20230601.gappssmtp.com header.i=@rivosinc-com.20230601.gappssmtp.com header.b="U7gLqHhi" X-Original-To: linux-kernel@vger.kernel.org Received: from mail-oo1-f46.google.com (mail-oo1-f46.google.com [209.85.161.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4776B14A87 for ; Fri, 29 Dec 2023 21:50:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=rivosinc.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rivosinc.com Received: by mail-oo1-f46.google.com with SMTP id 006d021491bc7-594e9135d82so1192127eaf.2 for ; Fri, 29 Dec 2023 13:50:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20230601.gappssmtp.com; s=20230601; t=1703886599; x=1704491399; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=vu5q4X23PA3gtec4TspOf+EMnf830wRQIwKELSXAAlg=; b=U7gLqHhiuIQYWeGy8p/wVg6RFUiZGuHY2zDoN/Zxrp+EMu2SYYls1SJoVSODfIJCE9 DC4fOfeykJZacOxXaEZ6WWXRCS7e8JuExy/za/ar+u5CosiVS/n6Z0qvAD2wduyTbCXA ho8LIPeOggRA+OJDkJOc3R0sNNWf7YLIjON6ajjPI0SFaxRzNiUcgjCegbmxPmWwz+FB a4nsPlQFp2nSA6fvg1LGNp/wAQtUelmBW208l8AMcxWd1XGan/Ac1i8y0FtPW5aytdPm X40tqOPLuFYi3pNh2mqBqIQRY6aa942fUkJYF2ttK/7Ea4QH0jua09SXhqUgvxvDbY5d AZGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703886599; x=1704491399; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vu5q4X23PA3gtec4TspOf+EMnf830wRQIwKELSXAAlg=; b=dsects6XUW5PQ/9m26YiiR/aZzxu9pckQbQJ9ym60Aeu9GTQHm50ASFtJVmwYn/XdU muWlGGKmG61kSTkA/zi15V+n5YoFpeW1Z+nhmiRROpMpnBYnalfl5y1lJNV1kBpnl0Co v/RXmZT+05Q1bTx6rhA6nTsQ34//uoYmpOtBUblwZFQEYkLu92lPcKfmGcQUn9ojtSKL JGNCpfmsdbveRLFrsFIEeCDcgT/fBqRfiDBrCy0r/kjspg9EIP8gOZ7EFP1K9//wSro3 xjE2lrP8FCd6+/GmtiZLTUVndC8/lCN3rFK3qJZ0mkWZsK/OwJbFSBkoYDn0spxccado o6GA== X-Gm-Message-State: AOJu0Ywi12wt0JtzrQNxKwxfetgs9JiZZYhlTpmcpA+FxD2gk5txTsxT d92PKQ/WfPQpDD7lyN3hAHFrmty/Mkw7lm3wv34PbjJYbT0= X-Received: by 2002:a4a:5b07:0:b0:595:3fd1:295b with SMTP id g7-20020a4a5b07000000b005953fd1295bmr263275oob.7.1703886599285; Fri, 29 Dec 2023 13:49:59 -0800 (PST) Received: from atishp.ba.rivosinc.com ([64.71.180.162]) by smtp.gmail.com with ESMTPSA id r126-20020a4a4e84000000b00594e32e4364sm1034751ooa.24.2023.12.29.13.49.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 Dec 2023 13:49:58 -0800 (PST) From: Atish Patra To: linux-kernel@vger.kernel.org Cc: Atish Patra , Albert Ou , Alexandre Ghiti , Andrew Jones , Anup Patel , Atish Patra , Conor Dooley , Guo Ren , Heiko Stuebner , kvm-riscv@lists.infradead.org, kvm@vger.kernel.org, linux-riscv@lists.infradead.org, Mark Rutland , Palmer Dabbelt , Paul Walmsley , Will Deacon Subject: [v2 00/10] RISC-V SBI v2.0 PMU improvements and Perf sampling in KVM guest Date: Fri, 29 Dec 2023 13:49:40 -0800 Message-Id: <20231229214950.4061381-1-atishp@rivosinc.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit This series implements SBI PMU improvements done in SBI v2.0[1] i.e. PMU snapshot and fw_read_hi() functions. SBI v2.0 introduced PMU snapshot feature which allows the SBI implementation to provide counter information (i.e. values/overflow status) via a shared memory between the SBI implementation and supervisor OS. This allows to minimize the number of traps in when perf being used inside a kvm guest as it relies on SBI PMU + trap/emulation of the counters. The current set of ratified RISC-V specification also doesn't allow scountovf to be trap/emulated by the hypervisor. The SBI PMU snapshot bridges the gap in ISA as well and enables perf sampling in the guest. However, LCOFI in the guest only works via IRQ filtering in AIA specification. That's why, AIA has to be enabled in the hardware (at least the Ssaia extension) in order to use the sampling support in the perf. Here are the patch wise implementation details. PATCH 1,6,7 : Generic cleanups/improvements. PATCH 2,3,10 : FW_READ_HI function implementation PATCH 4-5: Add PMU snapshot feature in sbi pmu driver PATCH 6-7: KVM implementation for snapshot and sampling in kvm guests The series is based on kvm-next and is available at: https://github.com/atishp04/linux/tree/kvm_pmu_snapshot_v2 The kvmtool patch is also available at: https://github.com/atishp04/kvmtool/tree/sscofpmf It also requires Ssaia ISA extension to be present in the hardware in order to get perf sampling support in the guest. In Qemu virt machine, it can be done by the following config. ``` -cpu rv64,sscofpmf=true,x-ssaia=true ``` There is no other dependencies on AIA apart from that. Thus, Ssaia must be disabled for the guest if AIA patches are not available. Here is the example command. ``` ./lkvm-static run -m 256 -c2 --console serial -p "console=ttyS0 earlycon" --disable-ssaia -k ./Image --debug ``` The series has been tested only in Qemu. Here is the snippet of the perf running inside a kvm guest. =================================================== $ perf record -e cycles -e instructions perf bench sched messaging -g 5 ... $ Running 'sched/messaging' benchmark: ... [ 45.928723] perf_duration_warn: 2 callbacks suppressed [ 45.929000] perf: interrupt took too long (484426 > 483186), lowering kernel.perf_event_max_sample_rate to 250 $ 20 sender and receiver processes per group $ 5 groups == 200 processes run Total time: 14.220 [sec] [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.117 MB perf.data (1942 samples) ] $ perf report --stdio $ To display the perf.data header info, please use --header/--header-only optio> $ $ $ Total Lost Samples: 0 $ $ Samples: 943 of event 'cycles' $ Event count (approx.): 5128976844 $ $ Overhead Command Shared Object Symbol > $ ........ ............... ........................... .....................> $ 7.59% sched-messaging [kernel.kallsyms] [k] memcpy 5.48% sched-messaging [kernel.kallsyms] [k] percpu_counter_ad> 5.24% sched-messaging [kernel.kallsyms] [k] __sbi_rfence_v02_> 4.00% sched-messaging [kernel.kallsyms] [k] _raw_spin_unlock_> 3.79% sched-messaging [kernel.kallsyms] [k] set_pte_range 3.72% sched-messaging [kernel.kallsyms] [k] next_uptodate_fol> 3.46% sched-messaging [kernel.kallsyms] [k] filemap_map_pages 3.31% sched-messaging [kernel.kallsyms] [k] handle_mm_fault 3.20% sched-messaging [kernel.kallsyms] [k] finish_task_switc> 3.16% sched-messaging [kernel.kallsyms] [k] clear_page 3.03% sched-messaging [kernel.kallsyms] [k] mtree_range_walk 2.42% sched-messaging [kernel.kallsyms] [k] flush_icache_pte =================================================== [1] https://github.com/riscv-non-isa/riscv-sbi-doc Changes from v1->v2: 1. Fixed warning/errors from patchwork CI. 2. Rebased on top of kvm-next. 3. Added Acked-by tags. Changes from RFC->v1: 1. Addressed all the comments on RFC series. 2. Removed PATCH2 and merged into later patches. 3. Added 2 more patches for minor fixes. 4. Fixed KVM boot issue without Ssaia and made sscofpmf in guest dependent on Ssaia in the host. Atish Patra (10): RISC-V: Fix the typo in Scountovf CSR name RISC-V: Add FIRMWARE_READ_HI definition drivers/perf: riscv: Read upper bits of a firmware counter RISC-V: Add SBI PMU snapshot definitions drivers/perf: riscv: Implement SBI PMU snapshot function RISC-V: KVM: No need to update the counter value during reset RISC-V: KVM: No need to exit to the user space if perf event failed RISC-V: KVM: Implement SBI PMU Snapshot feature RISC-V: KVM: Add perf sampling support for guests RISC-V: KVM: Support 64 bit firmware counters on RV32 arch/riscv/include/asm/csr.h | 5 +- arch/riscv/include/asm/errata_list.h | 2 +- arch/riscv/include/asm/kvm_vcpu_pmu.h | 14 +- arch/riscv/include/asm/sbi.h | 12 ++ arch/riscv/include/uapi/asm/kvm.h | 1 + arch/riscv/kvm/aia.c | 5 + arch/riscv/kvm/main.c | 1 + arch/riscv/kvm/vcpu.c | 8 +- arch/riscv/kvm/vcpu_onereg.c | 9 +- arch/riscv/kvm/vcpu_pmu.c | 246 ++++++++++++++++++++++++-- arch/riscv/kvm/vcpu_sbi_pmu.c | 15 +- drivers/perf/riscv_pmu.c | 1 + drivers/perf/riscv_pmu_sbi.c | 228 ++++++++++++++++++++++-- include/linux/perf/riscv_pmu.h | 6 + 14 files changed, 508 insertions(+), 45 deletions(-) -- 2.34.1