netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislav Fomichev <sdf@fomichev.me>
To: Quentin Monnet <quentin.monnet@netronome.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	netdev@vger.kernel.org, oss-drivers@netronome.com,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device
Date: Wed, 16 Jan 2019 09:15:45 -0800	[thread overview]
Message-ID: <20190116171545.GE726@mini-arch> (raw)
In-Reply-To: <20190116142119.8358-1-quentin.monnet@netronome.com>

On 01/16, Quentin Monnet wrote:
> 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.
Looks great! For the whole series:

Reviewed-by: Stanislav Fomichev <sdf@google.com>
> 
> 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 <acme@kernel.org>
> Cc: Jesper Dangaard Brouer <brouer@redhat.com>
> Cc: Stanislav Fomichev <sdf@google.com>
> 
> 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
> 

  parent reply	other threads:[~2019-01-16 17:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 14:21 [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 1/9] tools: bpftool: add basic probe capability, probe syscall availability Quentin Monnet
2019-01-17  0:28   ` Jakub Kicinski
2019-01-17 10:02     ` Quentin Monnet
2019-01-17 10:11       ` Daniel Borkmann
2019-01-16 14:21 ` [PATCH bpf-next v4 2/9] tools: bpftool: add probes for /proc/ eBPF parameters Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 3/9] tools: bpftool: add probes for kernel configuration options Quentin Monnet
2019-01-17  0:34   ` Jakub Kicinski
2019-01-17 10:03     ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 4/9] tools: bpftool: add probes for eBPF program types Quentin Monnet
2019-01-17  0:42   ` Jakub Kicinski
2019-01-17  9:27     ` Daniel Borkmann
2019-01-17 10:04       ` Quentin Monnet
2019-01-17 14:11     ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 5/9] tools: bpftool: add probes for eBPF map types Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 6/9] tools: bpftool: add probes for eBPF helper functions Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 7/9] tools: bpftool: add C-style "#define" output for probes Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 8/9] tools: bpftool: add probes for a network device Quentin Monnet
2019-01-16 14:42   ` Jesper Dangaard Brouer
2019-01-16 14:59     ` Quentin Monnet
2019-01-16 14:21 ` [PATCH bpf-next v4 9/9] tools: bpftool: add bash completion for bpftool probes Quentin Monnet
2019-01-16 17:15 ` Stanislav Fomichev [this message]
2019-01-17 10:06   ` [PATCH bpf-next v4 0/9] tools: bpftool: add probes for system and device Quentin Monnet
2019-01-17  0:55 ` Jakub Kicinski
2019-01-17  0:56   ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190116171545.GE726@mini-arch \
    --to=sdf@fomichev.me \
    --cc=acme@kernel.org \
    --cc=ast@kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.com \
    --cc=quentin.monnet@netronome.com \
    --cc=sdf@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).