From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Martin KaFai Lau <kafai@fb.com>
Cc: netdev@vger.kernel.org, Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Wang Nan <wangnan0@huawei.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH bpf-next v5 00/10] BTF: BPF Type Format
Date: Thu, 7 Jun 2018 17:25:24 -0300 [thread overview]
Message-ID: <20180607202524.GH17292@kernel.org> (raw)
In-Reply-To: <20180607200701.bvsjzoq56rnggwfd@kafai-mbp>
Em Thu, Jun 07, 2018 at 01:07:01PM -0700, Martin KaFai Lau escreveu:
> On Thu, Jun 07, 2018 at 04:30:29PM -0300, Arnaldo Carvalho de Melo wrote:
> > So this must be available in a newer llvm version? Which one?
> I should have put in the details in my last email or
> in the commit message, my bad.
> 1. The tools/testing/selftests/bpf/Makefile has the CLANG_FLAGS and
> LLC_FLAGS needed to compile the bpf prog. It requires a new
> "-mattr=dwarf" llc option which was added to the future
> llvm 7.0.
> Hence, I have been using the llvm's master in github which
> also has the llvm-objcopy.
> 2. The kernel's btf part only focus on the BPF map.
> Hence, the testing bpf program should have the map's key
> and map's value. e.g. tools/testing/selftests/bpf/test_btf_haskv.c
Thanks for the version required to test this, but where is this
test_btf_haskv.c file? Which tree? net-next?
Ok, just pulled torvalds/master and there it is. Gotcha.
struct bpf_map_def SEC("maps") __bpf_stdout__ = {
.type = BPF_MAP_TYPE_PERF_EVENT_ARRAY,
.key_size = sizeof(int),
.value_size = sizeof(u32),
.max_entries = __NR_CPUS__,
};
This map is in the above hello.c example, but I guess its way too simple
:-)
Ok, I'll test this at home in another machine where I have the llvm's
git repo.
- Arnaldo
next prev parent reply other threads:[~2018-06-07 20:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 22:55 [PATCH bpf-next v5 00/10] BTF: BPF Type Format Martin KaFai Lau
2018-04-18 22:55 ` [PATCH bpf-next v5 01/10] bpf: btf: Introduce BPF Type Format (BTF) Martin KaFai Lau
2018-04-18 22:55 ` [PATCH bpf-next v5 02/10] bpf: btf: Validate type reference Martin KaFai Lau
2018-04-18 22:55 ` [PATCH bpf-next v5 03/10] bpf: btf: Check members of struct/union Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 04/10] bpf: btf: Add pretty print capability for data with BTF type info Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 05/10] bpf: btf: Add BPF_BTF_LOAD command Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 06/10] bpf: btf: Add BPF_OBJ_GET_INFO_BY_FD support to BTF fd Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 07/10] bpf: btf: Add pretty print support to the basic arraymap Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 08/10] bpf: btf: Sync bpf.h and btf.h to tools/ Martin KaFai Lau
2018-04-18 22:56 ` [PATCH bpf-next v5 09/10] bpf: btf: Add BTF support to libbpf Martin KaFai Lau
2018-05-09 22:17 ` libbpf backward compatibility (was: [PATCH bpf-next v5 09/10] bpf: btf: Add BTF support to libbpf) Jakub Kicinski
2018-05-09 22:20 ` Jakub Kicinski
2018-04-18 22:56 ` [PATCH bpf-next v5 10/10] bpf: btf: Add BTF tests Martin KaFai Lau
2018-04-19 19:40 ` [PATCH bpf-next v5 00/10] BTF: BPF Type Format Arnaldo Carvalho de Melo
2018-04-19 20:58 ` Martin KaFai Lau
2018-06-05 21:25 ` Martin KaFai Lau
2018-06-06 12:33 ` Arnaldo Carvalho de Melo
2018-06-07 13:54 ` Arnaldo Carvalho de Melo
2018-06-07 14:03 ` Arnaldo Carvalho de Melo
2018-06-07 19:05 ` Martin KaFai Lau
2018-06-07 19:30 ` Arnaldo Carvalho de Melo
2018-06-07 20:07 ` Martin KaFai Lau
2018-06-07 20:25 ` Arnaldo Carvalho de Melo [this message]
2018-06-12 20:31 ` Arnaldo Carvalho de Melo
2018-06-12 20:41 ` Arnaldo Carvalho de Melo
2018-06-13 23:26 ` Martin KaFai Lau
2018-06-14 15:03 ` Arnaldo Carvalho de Melo
2018-06-14 16:22 ` Martin KaFai Lau
2018-06-14 17:18 ` Arnaldo Carvalho de Melo
2018-06-14 17:21 ` Alexei Starovoitov
2018-06-14 17:41 ` Arnaldo Carvalho de Melo
2018-06-14 17:47 ` Arnaldo Carvalho de Melo
2018-06-14 18:00 ` Arnaldo Carvalho de Melo
2018-06-15 4:56 ` Yonghong Song
2018-06-15 14:24 ` Arnaldo Carvalho de Melo
2018-06-15 16:06 ` Yonghong Song
2018-06-15 11:20 ` Bo YU
2018-04-19 23:57 ` Daniel Borkmann
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=20180607202524.GH17292@kernel.org \
--to=acme@kernel.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangnan0@huawei.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).