[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50a4f620-c9ad-d17f-07ee-d7c901cb76ed@isovalent.com>
Date: Thu, 12 Mar 2020 11:46:24 +0000
From: Quentin Monnet <quentin@...valent.com>
To: Song Liu <songliubraving@...com>, netdev@...r.kernel.org,
bpf@...r.kernel.org
Cc: john.fastabend@...il.com, kernel-team@...com, ast@...nel.org,
daniel@...earbox.net, arnaldo.melo@...il.com, jolsa@...nel.org
Subject: Re: [PATCH v2 bpf-next 1/3] bpftool: only build bpftool-prog-profile
if supported by clang
2020-03-11 15:18 UTC-0700 ~ Song Liu <songliubraving@...com>
> bpftoo-prog-profile requires clang to generate BTF for global variables.
Typo: bpftool (missing "l")
> When compared with older clang, skip this command. This is achieved by
> adding a new feature, clang-bpf-global-var, to tools/build/feature.
>
> Signed-off-by: Song Liu <songliubraving@...com>
Works great when clang is either too old or missing, thanks!
> diff --git a/tools/bpf/bpftool/prog.c b/tools/bpf/bpftool/prog.c
> index 576ddd82bc96..03b1979dfad8 100644
> --- a/tools/bpf/bpftool/prog.c
> +++ b/tools/bpf/bpftool/prog.c
> @@ -1545,6 +1545,8 @@ static int do_loadall(int argc, char **argv)
>
> static int do_profile(int argc, char **argv)
> {
> + fprintf(stdout, "bpftool prog profile command is not supported.\n"
> + "Please build bpftool with clang >= 10.0.0\n");
Nit: Can we use p_err() instead of fprintf(), and a single-line error
message please? To remain consistent and work with JSON output.
Thanks,
Quentin
Powered by blists - more mailing lists