summaryrefslogtreecommitdiff
path: root/tools/perf/arch/s390/entry/syscalls/syscall.tbl
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-01-23 08:07:02 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2022-01-23 08:07:02 +0200
commit67bfce0e01927859618b76ff5a36a7f23b412cef (patch)
tree0608ca6cc9c35059acd10454704346edcfdfbd7e /tools/perf/arch/s390/entry/syscalls/syscall.tbl
parent473aec0e1f84be97c7ea52c4266b7ef13ce36af3 (diff)
parent6b9b6413700e104934734b72a3be622a76923b98 (diff)
Merge tag 'trace-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull ftrace fix from Steven Rostedt: "Fix s390 breakage from sorting mcount tables. The latest merge of the tracing tree sorts the mcount table at build time. But s390 appears to do things differently (like always) and replaces the sorted table back to the original unsorted one. As the ftrace algorithm depends on it being sorted, bad things happen when it is not, and s390 experienced those bad things. Add a new config to tell the boot if the mcount table is sorted or not, and allow s390 to opt out of it" * tag 'trace-v5.17-3' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: ftrace: Fix assuming build time sort works for s390
Diffstat (limited to 'tools/perf/arch/s390/entry/syscalls/syscall.tbl')
0 files changed, 0 insertions, 0 deletions