Searched hist:"05 a06be722896e51f65dbbb6a3610f85a8353d6b" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/tools/bpf/bpftool/bash-completion/ |
| H A D | bpftool | diff 05a06be722896e51f65dbbb6a3610f85a8353d6b Wed Apr 05 08:21:17 CDT 2023 Quentin Monnet <quentin@isovalent.com> bpftool: Return an error on prog dumps if both CFG and JSON are required
We do not support JSON output for control flow graphs of programs with
bpftool. So far, requiring both the CFG and JSON output would result in
producing a null JSON object. It makes more sense to raise an error
directly when parsing command line arguments and options, so that users
know they won't get any output they might expect.
If JSON is required for the graph, we leave it to Graphviz instead:
# bpftool prog dump xlated <REF> visual | dot -Tjson
Suggested-by: Eduard Zingerman <eddyz87@gmail.com>
Signed-off-by: Quentin Monnet <quentin@isovalent.com>
Link: https://lore.kernel.org/r/20230405132120.59886-5-quentin@isovalent.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
|
| /openbmc/linux/tools/bpf/bpftool/ |
| H A D | prog.c | diff 05a06be722896e51f65dbbb6a3610f85a8353d6b Wed Apr 05 08:21:17 CDT 2023 Quentin Monnet <quentin@isovalent.com> bpftool: Return an error on prog dumps if both CFG and JSON are required
We do not support JSON output for control flow graphs of programs with
bpftool. So far, requiring both the CFG and JSON output would result in
producing a null JSON object. It makes more sense to raise an error
directly when parsing command line arguments and options, so that users
know they won't get any output they might expect.
If JSON is required for the graph, we leave it to Graphviz instead:
# bpftool prog dump xlated <REF> visual | dot -Tjson
Suggested-by: Eduard Zingerman <eddyz87@gmail.com>
Signed-off-by: Quentin Monnet <quentin@isovalent.com>
Link: https://lore.kernel.org/r/20230405132120.59886-5-quentin@isovalent.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
|