From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 389C0C43387 for ; Wed, 16 Jan 2019 14:21:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0050B20675 for ; Wed, 16 Jan 2019 14:21:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=netronome-com.20150623.gappssmtp.com header.i=@netronome-com.20150623.gappssmtp.com header.b="aj9lEn3q" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2403767AbfAPOVk (ORCPT ); Wed, 16 Jan 2019 09:21:40 -0500 Received: from mail-wr1-f67.google.com ([209.85.221.67]:45225 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733125AbfAPOVi (ORCPT ); Wed, 16 Jan 2019 09:21:38 -0500 Received: by mail-wr1-f67.google.com with SMTP id t6so7071566wrr.12 for ; Wed, 16 Jan 2019 06:21:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id; bh=OepEJ412uKsrgqp0wM9UpvfWqPfyuQpM98c/lXm7Zas=; b=aj9lEn3q9mGmwerg0Hrx1Ey1+eBK3sksguG6a13xj28Ga6SJJaXfXapjwaEK9hQlDZ 6yl+w7d7I9Ei4FUtqiZnSU4jklLYgLRlMcLXyUwK4U3JTm3Tql5jbyXe1MjLXCx/Gkrf /gzV83rqwpq0g3N6cvujv4yYhB02YutTRSDzo3btC9J7JsJ9S+6rGWzWo3j3CFJWoh6D Hs7isgUvcan+2UBvTdahuyBtHpcOrFS7vFh75nLyfs8VIR74MgQyEEvMnt88dEj/NT+V 6+xsHIrlowdKu16l8bRMBePa/y2ZoV87dJDrZoirFj7GKhXTfMo/ClB6U9JMgLZYX329 KjAg== 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; bh=OepEJ412uKsrgqp0wM9UpvfWqPfyuQpM98c/lXm7Zas=; b=X0PyiFH6lF8yGIvTP8hbhxy5BmBdNNqW3N4AjVGoTirB5g8Zg26GCPs+nlfPd6ojVP 4pYD3flVi3KRyarKv9Y2CwrLkjAndM2Nab22po8KO0fY1uIN04BR9gZLVN+Kg3aSv075 PrvHjH97n01OikVAuud5vxIb/ukVZbRRh4P3Ay57l0LdjuBIVBnivmI55SYOFVnQ+Mpq IFgQL+rgbQAhIRazJqWINcek3RQDBXPlxXEcY2cbhIBayBa7YGa4Eage8U6GMtJwblEI R3Ic41sNom0ko1OMyPJKh7h+v9JQeuCKCc2Fynb+FKVlicS1R5DYhkVfQ+FcgKN0AHgG 03Xw== X-Gm-Message-State: AJcUukfoiLrtwpUwvuL2gDGzBG1EVlsrc8W0pfYqbtG8ZzCkdZOrPGfw siqqQUQsEJ8WW8Y7iQuFm4Uahw== X-Google-Smtp-Source: ALg8bN7r58z/YuTQu++8X0rAsL+ymJBZHNktz3nu3qI3R35WrRFuxwGkGI/ijE4aVdqdaJYzVFOSRw== X-Received: by 2002:a5d:4f10:: with SMTP id c16mr8031693wru.177.1547648496385; Wed, 16 Jan 2019 06:21:36 -0800 (PST) Received: from cbtest32.netronome.com ([217.38.71.146]) by smtp.gmail.com with ESMTPSA id p6sm97412602wrx.50.2019.01.16.06.21.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Jan 2019 06:21:35 -0800 (PST) From: Quentin Monnet To: Alexei Starovoitov , Daniel Borkmann Cc: netdev@vger.kernel.org, oss-drivers@netronome.com, Quentin Monnet , Arnaldo Carvalho de Melo , Jesper Dangaard Brouer , Stanislav Fomichev Subject: [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device Date: Wed, 16 Jan 2019 14:21:10 +0000 Message-Id: <20190116142119.8358-1-quentin.monnet@netronome.com> X-Mailer: git-send-email 2.17.1 Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi, This set adds a new command to bpftool in order to dump a list of eBPF-related parameters for the system (or for a specific network device) to the console. Once again, this is based on a suggestion from Daniel. At this time, output includes: - Availability of bpf() system call - Availability of bpf() system call for unprivileged users - JIT status (enabled or not, with or without debugging traces) - JIT hardening status - JIT kallsyms exports status - Global memory limit for JIT compiler for unprivileged users - Status of kernel compilation options related to BPF features - Availability of known eBPF program types - Availability of known eBPF map types - Availability of known eBPF helper functions There are three different ways to dump this information at this time: - Plain output dumps probe results in plain text. It is the most flexible options for providing descriptive output to the user, but should not be relied upon for parsing the output. - JSON output is supported. - A third mode, available through the "macros" keyword appended to the command line, dumps some of those parameters (not all) as a series of "#define" directives, that can be included into a C header file for example. Probes for supported program and map types, and supported helpers, are directly added to libbpf, so that other applications (or selftests) can reuse them as necessary. If the user does not have root privileges (or more precisely, the CAP_SYS_ADMIN capability) detection will be erroneous for most parameters. Therefore, forbid non-root users to run the command. v4: - Probe bpf_jit_limit parameter (patch 2). - Probe some additional kernel config options (patch 3). - Minor fixes on patch 6. v3: - Do not probe kernel version in bpftool (just retrieve it to probe support for kprobes in libbpf). - Change the way results for helper support is displayed: now one list of compatible helpers for each program type (and C-style output gets a HAVE_PROG_TYPE_HELPER(prog_type, helper) macro to help with tests. See patches 6, 7. - Address other comments from feedback from v2 (please refer to individual patches' history). v2 (please also refer to individual patches' history): - Move probes for prog/map types, helpers, from bpftool to libbpf. - Move C-style output as a separate patch, and restrict it to a subset of collected information (bpf() availability, prog/map types, helpers). - Now probe helpers with all supported program types, and display a list of compatible program types (as supported on the system) for each helper. - NOT addressed: grouping compilation options for kernel into subsections (patch 3) (I don't see an easy way of grouping them at the moment, please see also the discussion on v1 thread). Cc: Arnaldo Carvalho de Melo Cc: Jesper Dangaard Brouer Cc: Stanislav Fomichev Quentin Monnet (9): tools: bpftool: add basic probe capability, probe syscall availability tools: bpftool: add probes for /proc/ eBPF parameters tools: bpftool: add probes for kernel configuration options tools: bpftool: add probes for eBPF program types tools: bpftool: add probes for eBPF map types tools: bpftool: add probes for eBPF helper functions tools: bpftool: add C-style "#define" output for probes tools: bpftool: add probes for a network device tools: bpftool: add bash completion for bpftool probes .../bpftool/Documentation/bpftool-cgroup.rst | 1 + .../bpftool/Documentation/bpftool-feature.rst | 85 ++ .../bpf/bpftool/Documentation/bpftool-map.rst | 1 + .../bpf/bpftool/Documentation/bpftool-net.rst | 1 + .../bpftool/Documentation/bpftool-perf.rst | 1 + .../bpftool/Documentation/bpftool-prog.rst | 1 + tools/bpf/bpftool/Documentation/bpftool.rst | 1 + tools/bpf/bpftool/bash-completion/bpftool | 19 + tools/bpf/bpftool/feature.c | 764 ++++++++++++++++++ tools/bpf/bpftool/main.c | 3 +- tools/bpf/bpftool/main.h | 4 + tools/bpf/bpftool/map.c | 4 +- tools/lib/bpf/Build | 2 +- tools/lib/bpf/libbpf.h | 14 + tools/lib/bpf/libbpf.map | 3 + tools/lib/bpf/libbpf_probes.c | 242 ++++++ 16 files changed, 1143 insertions(+), 3 deletions(-) create mode 100644 tools/bpf/bpftool/Documentation/bpftool-feature.rst create mode 100644 tools/bpf/bpftool/feature.c create mode 100644 tools/lib/bpf/libbpf_probes.c -- 2.17.1