From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andriin@fb.com>,
"alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>,
"andrii.nakryiko@gmail.com" <andrii.nakryiko@gmail.com>,
Song Liu <songliubraving@fb.com>,
"Alexei Starovoitov" <ast@fb.com>, Martin Lau <kafai@fb.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"acme@kernel.org" <acme@kernel.org>
Subject: Re: [PATCH v4 bpf-next 3/4] btf: expose API to work with raw btf_ext data
Date: Fri, 8 Feb 2019 19:50:19 +0000 [thread overview]
Message-ID: <8dc7238d-1824-ff8c-6e93-7a29579626cc@fb.com> (raw)
In-Reply-To: <20190208191939.3105592-4-andriin@fb.com>
On 2/8/19 11:19 AM, Andrii Nakryiko wrote:
> This patch changes struct btf_ext to retain original data in sequential
> block of memory, which makes it possible to expose
> btf_ext__get_raw_data() interface similar to btf__get_raw_data(), allowing
> users of libbpf to get access to raw representation of .BTF.ext section.
>
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2019-02-08 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 19:19 [PATCH v4 bpf-next 0/4] tools/btf: extend libbpf APIs to work with btf w/o kernel Andrii Nakryiko
2019-02-08 19:19 ` [PATCH v4 bpf-next 1/4] btf: separate btf creation and loading Andrii Nakryiko
2019-02-08 19:19 ` [PATCH v4 bpf-next 2/4] btf: expose API to work with raw btf data Andrii Nakryiko
2019-02-08 19:19 ` [PATCH v4 bpf-next 3/4] btf: expose API to work with raw btf_ext data Andrii Nakryiko
2019-02-08 19:50 ` Yonghong Song [this message]
2019-02-08 19:19 ` [PATCH v4 bpf-next 4/4] tools/bpf: remove btf__get_strings() superseded by raw data API Andrii Nakryiko
2019-02-08 20:08 ` [PATCH v4 bpf-next 0/4] tools/btf: extend libbpf APIs to work with btf w/o kernel Alexei Starovoitov
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=8dc7238d-1824-ff8c-6e93-7a29579626cc@fb.com \
--to=yhs@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@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;
as well as URLs for NNTP newsgroup(s).