diff options
Diffstat (limited to 'tools/include/uapi/linux/bpf.h')
-rw-r--r-- | tools/include/uapi/linux/bpf.h | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/tools/include/uapi/linux/bpf.h b/tools/include/uapi/linux/bpf.h index 597afdbc1ab9..8050caea7495 100644 --- a/tools/include/uapi/linux/bpf.h +++ b/tools/include/uapi/linux/bpf.h | |||
@@ -232,6 +232,20 @@ enum bpf_attach_type { | |||
232 | */ | 232 | */ |
233 | #define BPF_F_STRICT_ALIGNMENT (1U << 0) | 233 | #define BPF_F_STRICT_ALIGNMENT (1U << 0) |
234 | 234 | ||
235 | /* If BPF_F_ANY_ALIGNMENT is used in BPF_PROF_LOAD command, the | ||
236 | * verifier will allow any alignment whatsoever. On platforms | ||
237 | * with strict alignment requirements for loads ands stores (such | ||
238 | * as sparc and mips) the verifier validates that all loads and | ||
239 | * stores provably follow this requirement. This flag turns that | ||
240 | * checking and enforcement off. | ||
241 | * | ||
242 | * It is mostly used for testing when we want to validate the | ||
243 | * context and memory access aspects of the verifier, but because | ||
244 | * of an unaligned access the alignment check would trigger before | ||
245 | * the one we are interested in. | ||
246 | */ | ||
247 | #define BPF_F_ANY_ALIGNMENT (1U << 1) | ||
248 | |||
235 | /* when bpf_ldimm64->src_reg == BPF_PSEUDO_MAP_FD, bpf_ldimm64->imm == fd */ | 249 | /* when bpf_ldimm64->src_reg == BPF_PSEUDO_MAP_FD, bpf_ldimm64->imm == fd */ |
236 | #define BPF_PSEUDO_MAP_FD 1 | 250 | #define BPF_PSEUDO_MAP_FD 1 |
237 | 251 | ||