All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
	Jonathan Corbet <corbet@lwn.net>,
	grantseltzer <grantseltzer@gmail.com>
Subject: Re: [PATCH bpf-next] Add table of BPF program types to docs
Date: Wed, 24 Aug 2022 11:24:41 +0100	[thread overview]
Message-ID: <m2fshmym52.fsf@gmail.com> (raw)
In-Reply-To: <CAEf4BzaujwgDXm+05MuGr_ouAseGGFg50Cxb83hHeWHX7bCk6A@mail.gmail.com> (Andrii Nakryiko's message of "Tue, 23 Aug 2022 15:53:36 -0700")

Andrii Nakryiko <andrii.nakryiko@gmail.com> writes:

> On Tue, Aug 23, 2022 at 9:56 AM Donald Hunter <donald.hunter@gmail.com> wrote:
>>
>> Extend the BPF program types documentation with a table of
>> program types, attach points and ELF section names.
>>
>> The program_types.csv file is generated from tools/lib/bpf/libbpf.c
>> and a script is included for regenerating the .csv file.
>>
>> I have not integrated the script into the doc build but if that
>> is desirable then please suggest the preferred way to do so.
>>
>> Signed-off-by: Donald Hunter <donald.hunter@gmail.com>
>> ---
>
> It does seem cleaner to generate this .csv during docs build, instead
> of having to manually regenerate it all the time? Should we also put
> it under Documentation/bpf/libbpf/ as it's libbpf-specific? Having it
> under libbpf subdir would also make it simpler to expose it in libbpf
> docs at libbpf.readthedocs.io/

Agreed about generating the .csv as part of the doc build. I will look
at adding it to the docs Makefile.

I'm happy to put it in Documentation/bpf/libbpf and link to it from
Documentation/bpf/programs.rst.

> We can probably also establish some special comment format next to
> SEC_DEF() to specify the format of those "extras", I think it would be
> useful for users. WDYT?

Yes this would be a useful addition. Are the extras always for
auto-attach? If so, then I can add that to the rules.

I'd prefer to modify the existing ELF section name column to replace '+'
with extras since the table is already wide.

> CC'ing Grant as well, who worked on building libbpf docs.

  reply	other threads:[~2022-08-24 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 13:22 [PATCH bpf-next] Add table of BPF program types to docs Donald Hunter
2022-08-23 22:53 ` Andrii Nakryiko
2022-08-24 10:24   ` Donald Hunter [this message]
2022-08-25 20:29     ` Andrii Nakryiko

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=m2fshmym52.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=grantseltzer@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    /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.