aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/scripts/bpf_helpers_doc.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2020-03-30 19:35:52 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2020-03-30 19:35:52 -0700
commit2853d5fafb1e21707e89aa2e227c90bb2c1ea4a9 (patch)
treefc8243bcf4a75902ef843ec65fc06a9d65b187e1 /scripts/bpf_helpers_doc.py
parentMerge tag 'x86-entry-2020-03-30' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (diff)
parentx86/split_lock: Avoid runtime reads of the TEST_CTRL MSR (diff)
downloadwireguard-linux-2853d5fafb1e21707e89aa2e227c90bb2c1ea4a9.tar.xz
wireguard-linux-2853d5fafb1e21707e89aa2e227c90bb2c1ea4a9.zip
Merge tag 'x86-splitlock-2020-03-30' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull x86 splitlock updates from Thomas Gleixner: "Support for 'split lock' detection: Atomic operations (lock prefixed instructions) which span two cache lines have to acquire the global bus lock. This is at least 1k cycles slower than an atomic operation within a cache line and disrupts performance on other cores. Aside of performance disruption this is a unpriviledged form of DoS. Some newer CPUs have the capability to raise an #AC trap when such an operation is attempted. The detection is by default enabled in warning mode which will warn once when a user space application is caught. A command line option allows to disable the detection or to select fatal mode which will terminate offending applications with SIGBUS" * tag 'x86-splitlock-2020-03-30' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/split_lock: Avoid runtime reads of the TEST_CTRL MSR x86/split_lock: Rework the initialization flow of split lock detection x86/split_lock: Enable split lock detection by kernel
Diffstat (limited to 'scripts/bpf_helpers_doc.py')
0 files changed, 0 insertions, 0 deletions