All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Monnet <quentin.monnet@netronome.com>
To: Stanislav Fomichev <sdf@fomichev.me>
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: [oss-drivers] Re: [PATCH bpf-next 0/8] tools: bpftool: add probes for system and device
Date: Fri, 14 Dec 2018 18:41:29 +0000	[thread overview]
Message-ID: <656b0d7e-6317-5446-b90f-79d97b78641d@netronome.com> (raw)
In-Reply-To: <20181214182112.GB32470@mini-arch.hsd1.ca.comcast.net>

2018-12-14 10:21 UTC-0800 ~ Stanislav Fomichev <sdf@fomichev.me>
> On 12/14, Quentin Monnet wrote:
>> 2018-12-13 12:19 UTC+0000 ~ Quentin Monnet <quentin.monnet@netronome.com>
>>> Hi,
>>> This set add 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:
>>>
>>
>> So as a reminder this one comes from an actual probe with the syscall...
>>
>>>     - Availability of bpf() system call
>>
>> ... those 4 are read from procfs...
>>
>>>     - 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
>>
>> ... these are read from /boot/config-$(uname -r)...
>>
>>>     - Status of kernel compilation options related to BPF features
>>
>> ... this from uname()...
>>
>>>     - Release number of the running kernel
>>
>> ... and the remaining ones are probed with minimal BPF programs.
>>
>>>     - Availability of known eBPF program types
>>>     - Availability of known eBPF map types
>>>     - Availability of known eBPF helper functions
>>
>> As discussed with Stanislav and Daniel, some of the probing should
>> probably be moved to libbpf instead for the next version of this set. As
>> I see it, I could move probing to libbpf for:
>>
>> - BPF prog and map types
>> - BPF helper functions
>> - bpf() syscall availability
>>
>> I do not think kernel compile options, or kernel release number, should
>> go to libbpf, they're probably better in bpftool. I'm unsure about the
> +1
> Kernel + /proc stuff can probably live in bpftool.
> 
>> procfs parameters, I'm considering leaving them in bpftool for now. Do
>> others have an opinion about this?
> Maybe start with adding prog/map/helpers probes to the libbpf
> (+ifindex)?

Agree with it, I'll work on a new version for next week. Thanks!

  reply	other threads:[~2018-12-14 18:41 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 12:19 [PATCH bpf-next 0/8] tools: bpftool: add probes for system and device Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 1/8] tools: bpftool: add basic probe capability, probe syscall and kversion Quentin Monnet
2018-12-14  2:50   ` Stanislav Fomichev
2018-12-14 11:27     ` Quentin Monnet
2018-12-14 18:45       ` Stanislav Fomichev
2018-12-15  3:31         ` Quentin Monnet
2018-12-14 23:35   ` Daniel Borkmann
2018-12-15  3:31     ` Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 2/8] tools: bpftool: add probes for /proc/ eBPF parameters Quentin Monnet
2018-12-14  2:58   ` Stanislav Fomichev
2018-12-14 11:27     ` Quentin Monnet
2018-12-14 23:40   ` Daniel Borkmann
2018-12-15  3:31     ` Quentin Monnet
2018-12-16  0:14       ` Daniel Borkmann
2018-12-17 10:44         ` Quentin Monnet
2018-12-17 11:11           ` Daniel Borkmann
2018-12-13 12:19 ` [PATCH bpf-next 3/8] tools: bpftool: add probes for kernel configuration options Quentin Monnet
2018-12-14 23:56   ` Daniel Borkmann
2018-12-15  3:32     ` Quentin Monnet
2018-12-19 18:49       ` Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 4/8] tools: bpftool: add probes for eBPF program types Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 5/8] tools: bpftool: add probes for eBPF map types Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 6/8] tools: bpftool: add probes for eBPF helper functions Quentin Monnet
2018-12-15  0:08   ` Daniel Borkmann
2018-12-15  3:32     ` Quentin Monnet
2018-12-15 23:57       ` Daniel Borkmann
2018-12-17 10:18         ` Quentin Monnet
2018-12-18  0:42           ` Daniel Borkmann
2018-12-19 19:02             ` Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 7/8] tools: bpftool: add probes for a network device Quentin Monnet
2018-12-13 12:19 ` [PATCH bpf-next 8/8] tools: bpftool: add bash completion for bpftool probes Quentin Monnet
2018-12-13 13:03 ` [PATCH bpf-next 0/8] tools: bpftool: add probes for system and device Arnaldo Carvalho de Melo
2018-12-13 13:49   ` Debugging eBPF was: " Arnaldo Carvalho de Melo
2018-12-13 20:55     ` Alexei Starovoitov
2018-12-14 13:39       ` Arnaldo Carvalho de Melo
2018-12-14 11:53 ` Quentin Monnet
2018-12-14 18:21   ` Stanislav Fomichev
2018-12-14 18:41     ` Quentin Monnet [this message]
2018-12-14 14:00 ` Arnaldo Carvalho de Melo
2018-12-14 14:56   ` Quentin Monnet
2018-12-14 17:26     ` Arnaldo Carvalho de Melo

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=656b0d7e-6317-5446-b90f-79d97b78641d@netronome.com \
    --to=quentin.monnet@netronome.com \
    --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=sdf@fomichev.me \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.