Message ID | 20200427141816.16703-1-eesposit@redhat.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <SRS0=SmUC=6L=vger.kernel.org=kvm-owner@kernel.org> Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 406211667 for <patchwork-kvm@patchwork.kernel.org>; Mon, 27 Apr 2020 14:18:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1D7D9206B9 for <patchwork-kvm@patchwork.kernel.org>; Mon, 27 Apr 2020 14:18:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="VqdAJO8f" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727771AbgD0OSe (ORCPT <rfc822;patchwork-kvm@patchwork.kernel.org>); Mon, 27 Apr 2020 10:18:34 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:33862 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727817AbgD0OSd (ORCPT <rfc822;kvm@vger.kernel.org>); Mon, 27 Apr 2020 10:18:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587997111; 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: content-transfer-encoding:content-transfer-encoding; bh=6l7ofSviSFO9MOFB06VMi9Ry2dYY3AhTTbA+TNMcpw4=; b=VqdAJO8fy7NsR6b0Sxv0a8rMpNrIjPNvZvHHZXhCZ7UZkxaRKVzNkDpkNhUshJgDkWlHtI fcz7j3Po0gSMjwGpURisuI/c+KrC7WTBOkJK6K3lro01uJwANy4oKvI6R/hDgMqYcGLLGS RWTd22urV+e2Pl6ZjtyKObTY90Y/Vho= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-301-mmDj8y51NCCfWRdSJSpazg-1; Mon, 27 Apr 2020 10:18:26 -0400 X-MC-Unique: mmDj8y51NCCfWRdSJSpazg-1 Received: by mail-wr1-f71.google.com with SMTP id j22so10640241wrb.4 for <kvm@vger.kernel.org>; Mon, 27 Apr 2020 07:18:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=6l7ofSviSFO9MOFB06VMi9Ry2dYY3AhTTbA+TNMcpw4=; b=RxStMcE9yX8L0QIrLERUPKjEClu4x4d1Vt5Y7kN19QHxgn0ziCemnmFEWpm+Dq7Yxq cmYtHbJfCrD3ZL3Hte+MM+g1a3SyCFjJrxG7Qoh8H7F7W7E3zNVml5Ujb+FN7+ITcnek x+NJo5c13EXBwSIB0NTongoolZIiLy56N96NCAzQutDNCj/qLS78UyDgjUThcYiHBYWJ 00PZf54qjHIcRqhBcgi72n2qp3XwREdvk0nJ8GXa5gEwI+nGMUgFDobgCA5CY/al1Z0a KTW6A+M5MiUlcLAmn3PHxJgGJTNR1btRlYk00+FG6wLk/7NrnT4si2yKjxWXETRdWtnU 7LQQ== X-Gm-Message-State: AGi0PuaRD9VyZQNhpRPMN/P/04O50sVTTioA2/iQZyKRp8fAd/n+fM7U bTYwwhBYSNqELmje1+QNWATaWtSRaR5yxLuQB4lpdyWBp2F0bEzgDBFUPfCAeBxbM960yV01w3k U7KT6qJ/Vkssg X-Received: by 2002:a1c:4c10:: with SMTP id z16mr26738337wmf.77.1587997104525; Mon, 27 Apr 2020 07:18:24 -0700 (PDT) X-Google-Smtp-Source: APiQypIHsnAsMxrnH0esIeaBPSv8S0Ym8kCw8qMYEwffVUW4cRvvHb2TeEAv2EODBP+Vj0xJksemYA== X-Received: by 2002:a1c:4c10:: with SMTP id z16mr26738311wmf.77.1587997104199; Mon, 27 Apr 2020 07:18:24 -0700 (PDT) Received: from localhost.localdomain.com ([194.230.155.207]) by smtp.gmail.com with ESMTPSA id 1sm15914570wmz.13.2020.04.27.07.18.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Apr 2020 07:18:23 -0700 (PDT) From: Emanuele Giuseppe Esposito <eesposit@redhat.com> To: kvm@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org, mst@redhat.com, borntraeger@de.ibm.com, Paolo Bonzini <pbonzini@redhat.com>, Emanuele Giuseppe Esposito <eesposit@redhat.com> Subject: [RFC PATCH 0/5] Statsfs: a new ram-based file sytem for Linux kernel statistics Date: Mon, 27 Apr 2020 16:18:11 +0200 Message-Id: <20200427141816.16703-1-eesposit@redhat.com> X-Mailer: git-send-email 2.25.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: <kvm.vger.kernel.org> X-Mailing-List: kvm@vger.kernel.org |
Series |
Statsfs: a new ram-based file sytem for Linux kernel statistics
|
expand
|
There is currently no common way for Linux kernel subsystems to expose statistics to userspace shared throughout the Linux kernel; subsystems have to take care of gathering and displaying statistics by themselves, for example in the form of files in debugfs. For example KVM has its own code section that takes care of this in virt/kvm/kvm_main.c, where it sets up debugfs handlers for displaying values and aggregating them from various subfolders to obtain information about the system state (i.e. displaying the total number of exits, calculated by summing all exits of all cpus of all running virtual machines). Allowing each section of the kernel to do so has two disadvantages. First, it will introduce redundant code. Second, debugfs is anyway not the right place for statistics (for example it is affected by lockdown) In this patch series I introduce statsfs, a synthetic ram-based virtual filesystem that takes care of gathering and displaying statistics for the Linux kernel subsystems. The file system is mounted on /sys/kernel/stats and would be already used by kvm. Statsfs was initially introduced by Paolo Bonzini [1]. Statsfs offers a generic and stable API, allowing any kind of directory/file organization and supporting multiple kind of aggregations (not only sum, but also average, max, min and count_zero) and data types (all unsigned and signed types plus boolean). The implementation, which is a generalization of KVM’s debugfs statistics code, takes care of gathering and displaying information at run time; users only need to specify the values to be included in each source. Statsfs would also be a different mountpoint from debugfs, and would not suffer from limited access due to the security lock down patches. Its main function is to display each statistics as a file in the desired folder hierarchy defined through the API. Statsfs files can be read, and possibly cleared if their file mode allows it. Statsfs has two main components: the public API defined by include/linux/statsfs.h, and the virtual file system which should end up in /sys/kernel/stats. The API has two main elements, values and sources. Kernel subsystems like KVM can use the API to create a source, add child sources/values/aggregates and register it to the root source (that on the virtual fs would be /sys/kernel/statsfs). Sources are created via statsfs_source_create(), and each source becomes a directory in the file system. Sources form a parent-child relationship; root sources are added to the file system via statsfs_source_register(). Every other source is added to or removed from a parent through the statsfs_source_add_subordinate and statsfs_source_remote_subordinate APIs. Once a source is created and added to the tree (via add_subordinate), it will be used to compute aggregate values in the parent source. Values represent quantites that are gathered by the statsfs user. Examples of values include the number of vm exits of a given kind, the amount of memory used by some data structure, the length of the longest hash table chain, or anything like that. Values are defined with the statsfs_source_add_values function. Each value is defined by a struct statsfs_value; the same statsfs_value can be added to many different sources. A value can be considered "simple" if it fetches data from a user-provided location, or "aggregate" if it groups all values in the subordinates sources that include the same statsfs_value. For more information, please consult the kerneldoc documentation in patch 2 and the sample uses in the kunit tests and in KVM. This series of patches is based on my previous series "libfs: group and simplify linux fs code" and the single patch sent to kvm "kvm_host: unify VM_STAT and VCPU_STAT definitions in a single place". The former simplifies code duplicated in debugfs and tracefs (from which statsfs is based on), the latter groups all macros definition for statistics in kvm in a single common file shared by all architectures. Patch 1 adds a new refcount and kref destructor wrappers that take a semaphore, as those are used later by statsfs. Patch 2 introduces the statsfs API, patch 3 provides extensive tests that can also be used as example on how to use the API and patch 4 adds the file system support. Finally, patch 5 provides a real-life example of statsfs usage in KVM. [1] https://lore.kernel.org/kvm/5d6cdcb1-d8ad-7ae6-7351-3544e2fa366d@redhat.com/?fbclid=IwAR18LHJ0PBcXcDaLzILFhHsl3qpT3z2vlG60RnqgbpGYhDv7L43n0ZXJY8M Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Emanuele Giuseppe Esposito (5): refcount, kref: add dec-and-test wrappers for rw_semaphores statsfs API: create, add and remove statsfs sources and values kunit: tests for statsfs API statsfs fs: virtual fs to show stats to the end-user kvm_main: replace debugfs with statsfs arch/arm64/kvm/guest.c | 2 +- arch/mips/kvm/mips.c | 2 +- arch/powerpc/kvm/book3s.c | 6 +- arch/powerpc/kvm/booke.c | 8 +- arch/s390/kvm/kvm-s390.c | 16 +- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/Makefile | 2 +- arch/x86/kvm/debugfs.c | 64 -- arch/x86/kvm/statsfs.c | 49 ++ arch/x86/kvm/x86.c | 6 +- fs/Kconfig | 13 + fs/Makefile | 1 + fs/statsfs/Makefile | 6 + fs/statsfs/inode.c | 337 ++++++++++ fs/statsfs/internal.h | 35 + fs/statsfs/statsfs-tests.c | 1067 +++++++++++++++++++++++++++++++ fs/statsfs/statsfs.c | 780 ++++++++++++++++++++++ include/linux/kref.h | 11 + include/linux/kvm_host.h | 39 +- include/linux/refcount.h | 2 + include/linux/statsfs.h | 234 +++++++ include/uapi/linux/magic.h | 1 + lib/refcount.c | 32 + tools/lib/api/fs/fs.c | 21 + virt/kvm/arm/arm.c | 2 +- virt/kvm/kvm_main.c | 314 ++------- 26 files changed, 2670 insertions(+), 382 deletions(-) delete mode 100644 arch/x86/kvm/debugfs.c create mode 100644 arch/x86/kvm/statsfs.c create mode 100644 fs/statsfs/Makefile create mode 100644 fs/statsfs/inode.c create mode 100644 fs/statsfs/internal.h create mode 100644 fs/statsfs/statsfs-tests.c create mode 100644 fs/statsfs/statsfs.c create mode 100644 include/linux/statsfs.h