From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexei Starovoitov <ast@fb.com>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Yonghong Song <yhs@fb.com>, Martin Lau <kafai@fb.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"dwarves@vger.kernel.org" <dwarves@vger.kernel.org>
Subject: Re: pahole: soliciting naming suggestion for struct btf rename
Date: Fri, 15 Feb 2019 14:25:15 -0300 [thread overview]
Message-ID: <20190215172515.GC31177@kernel.org> (raw)
In-Reply-To: <b156837f-ed18-caf6-7120-5ecfabd4c5ed@fb.com>
Em Fri, Feb 15, 2019 at 05:17:27PM +0000, Alexei Starovoitov escreveu:
> On 2/14/19 4:47 AM, Arnaldo Carvalho de Melo wrote:
> > I wonder if we should have a libbtf, with the same licensing as libbpf,
> > as, for instance, pahole would be interested only in the btf parts, be
> > it encoding, loading and pretty printing.
>
> I don't think it's possible to do such split.
> .btf.ext section only makes sense together with bpf prog.
Well, that part, that is not about types and only makes sense together
with the BPF parts could stay in libbpf, no?
- Arnaldo
next prev parent reply other threads:[~2019-02-15 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 5:43 pahole: soliciting naming suggestion for struct btf rename Andrii Nakryiko
2019-02-14 12:47 ` Arnaldo Carvalho de Melo
2019-02-14 13:11 ` Arnaldo Carvalho de Melo
2019-02-14 13:20 ` Arnaldo Carvalho de Melo
2019-02-14 14:01 ` Arnaldo Carvalho de Melo
2019-02-15 4:37 ` Andrii Nakryiko
2019-02-15 17:15 ` Arnaldo Carvalho de Melo
2019-02-15 17:25 ` Andrii Nakryiko
2019-02-15 17:43 ` Arnaldo Carvalho de Melo
2019-02-15 17:17 ` Alexei Starovoitov
2019-02-15 17:25 ` Arnaldo Carvalho de Melo [this message]
2019-02-15 18:47 ` Alexei Starovoitov
2019-02-15 20:21 ` Daniel Borkmann
2019-02-18 12:44 ` 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=20190215172515.GC31177@kernel.org \
--to=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=kafai@fb.com \
--cc=yhs@fb.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