From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH v3 bpf-next 0/5] bpftool: Support dumping a map with btf_vmlinux_value_type_id
Date: Wed, 15 Jan 2020 15:26:28 -0800 [thread overview]
Message-ID: <20200115232626.x5qzdvmx2d3d4abl@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200115230012.1100525-1-kafai@fb.com>
On Wed, Jan 15, 2020 at 03:00:12PM -0800, Martin KaFai Lau wrote:
> When a map is storing a kernel's struct, its
> map_info->btf_vmlinux_value_type_id is set. The first map type
> supporting it is BPF_MAP_TYPE_STRUCT_OPS.
>
> This series adds support to dump this kind of map with BTF.
> The first two patches are bug fixes which are only applicable to
> bpf-next.
>
> Please see individual patches for details.
>
> v3:
> - Remove unnecessary #include "libbpf_internal.h" from patch 5
I think the subj of patch 3 is fine as-is.
Applied. Thanks
prev parent reply other threads:[~2020-01-15 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 23:00 [PATCH v3 bpf-next 0/5] bpftool: Support dumping a map with btf_vmlinux_value_type_id Martin KaFai Lau
2020-01-15 23:00 ` [PATCH v3 bpf-next 1/5] bpftool: Fix a leak of btf object Martin KaFai Lau
2020-01-15 23:00 ` [PATCH v3 bpf-next 2/5] bpftool: Fix missing BTF output for json during map dump Martin KaFai Lau
2020-01-15 23:00 ` [PATCH v3 bpf-next 3/5] libbpf: Expose bpf_find_kernel_btf as a LIBBPF_API Martin KaFai Lau
2020-01-15 23:00 ` [PATCH v3 bpf-next 4/5] bpftool: Add struct_ops map name Martin KaFai Lau
2020-01-15 23:00 ` [PATCH v3 bpf-next 5/5] bpftool: Support dumping a map with btf_vmlinux_value_type_id Martin KaFai Lau
2020-01-15 23:26 ` Alexei Starovoitov [this message]
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=20200115232626.x5qzdvmx2d3d4abl@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=netdev@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.