diff options
| author | 2021-10-01 15:31:51 -0700 | |
|---|---|---|
| committer | 2021-10-01 15:31:51 -0700 | |
| commit | d636c8da2d60cc4841ebd7b6e6a02db5c33e11e4 (patch) | |
| tree | 99c4e3b27c85b415115fb1f648e7d663d4f1f669 /drivers/net/wwan/iosm/iosm_ipc_flash.c | |
| parent | bpf/tests: Add test of LDX_MEM with operand aliasing (diff) | |
| parent | selftests/bpf: Use BTF-defined key/value for map definitions (diff) | |
| download | linux-dev-d636c8da2d60cc4841ebd7b6e6a02db5c33e11e4.tar.xz linux-dev-d636c8da2d60cc4841ebd7b6e6a02db5c33e11e4.zip | |
Merge branch 'libbpf: Support uniform BTF-defined key/value specification across all BPF maps'
Hengqi Chen says:
====================
Currently a bunch of (usually pretty specialized) BPF maps do not support
specifying BTF types for they key and value. For such maps, specifying
their definition like this:
struct {
__uint(type, BPF_MAP_TYPE_PERF_EVENT_ARRAY);
__type(key, int);
__type(value, int);
} my_perf_buf SEC(".maps");
Would actually produce warnings about retrying BPF map creation without BTF.
Users are forced to know such nuances and use __uint(key_size, 4) instead.
This is non-uniform, annoying, and inconvenient.
This patch set teaches libbpf to recognize those specialized maps and removes
BTF type IDs when creating BPF map. Also, update existing BPF selftests to
exericse this change.
====================
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Diffstat (limited to 'drivers/net/wwan/iosm/iosm_ipc_flash.c')
0 files changed, 0 insertions, 0 deletions
