aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/bpf_helpers_doc.py
diff options
context:
space:
mode:
authorAlexei Starovoitov <[email protected]>2020-02-25 00:12:21 +0000
committerAlexei Starovoitov <[email protected]>2020-02-25 00:20:10 +0000
commit80a836c2506b2b249a9934fbe373eb7a4a98db86 (patch)
tree38d6b44dc8654900cfb0e735cd8d027ce00d4e53 /scripts/bpf_helpers_doc.py
parentMerge tag 'sched-for-bpf-2020-02-20' of git://git.kernel.org/pub/scm/linux/ke... (diff)
parentbpf/stackmap: Dont trylock mmap_sem with PREEMPT_RT and interrupts disabled (diff)
downloadkernel-80a836c2506b2b249a9934fbe373eb7a4a98db86.tar.gz
kernel-80a836c2506b2b249a9934fbe373eb7a4a98db86.zip
Merge branch 'BPF_and_RT'
Thomas Gleixner says: ==================== This is the third version of the BPF/RT patch set which makes both coexist nicely. The long explanation can be found in the cover letter of the V1 submission: https://lore.kernel.org/r/[email protected] V2 is here: https://lore.kernel.org/r/[email protected] The following changes vs. V2 have been made: - Rebased to bpf-next, adjusted to the lock changes in the hashmap code. - Split the preallocation enforcement patch for instrumentation type BPF programs into two pieces: 1) Emit a one-time warning on !RT kernels when any instrumentation type BPF program uses run-time allocation. Emit also a corresponding warning in the verifier log. But allow the program to run for backward compatibility sake. After a grace period this should be enforced. 2) On RT reject such programs because on RT the memory allocator cannot be called from truly atomic contexts. - Fixed the fallout from V2 as reported by Alexei and 0-day - Removed the redundant preempt_disable() from trace_call_bpf() - Removed the unused export of trace_call_bpf() ==================== Signed-off-by: Alexei Starovoitov <[email protected]>
Diffstat (limited to 'scripts/bpf_helpers_doc.py')
0 files changed, 0 insertions, 0 deletions