diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-06-12 11:34:49 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-06-12 11:34:49 -0700 |
| commit | 191aaf6cc4a7db907520f18af3a90b260e7dd091 (patch) | |
| tree | 68d058dcde0ab64562e528ea4281dc69205f5da3 /samples/configfs | |
| parent | 768895fb774d7af32d17cf3a455b0bd6df272f14 (diff) | |
| parent | a8383dfb2138742a1bb77b481ada047aededa2ba (diff) | |
| download | linux-191aaf6cc4a7db907520f18af3a90b260e7dd091.tar.bz2 | |
Merge tag 'perf-urgent-2021-06-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull perf fixes from Ingo Molnar:
"Misc fixes:
- Fix the NMI watchdog on ancient Intel CPUs
- Remove a misguided, NMI-unsafe KASAN callback from the NMI-safe
irq_work path used by perf.
- Fix uncore events on Ice Lake servers.
- Someone booted maxcpus=1 on an SNB-EP, and the uncore driver
emitted warnings and was probably buggy. Fix it.
- KCSAN found a genuine data race in the core perf code. Somewhat
ironically the bug was introduced through a recent race fix. :-/
In our defense, the new race window was much more narrow. Fix it"
* tag 'perf-urgent-2021-06-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
x86/nmi_watchdog: Fix old-style NMI watchdog regression on old Intel CPUs
irq_work: Make irq_work_queue() NMI-safe again
perf/x86/intel/uncore: Fix M2M event umask for Ice Lake server
perf/x86/intel/uncore: Fix a kernel WARNING triggered by maxcpus=1
perf: Fix data race between pin_count increment/decrement
Diffstat (limited to 'samples/configfs')
0 files changed, 0 insertions, 0 deletions