diff options
| author |   Peter Zijlstra <peterz@infradead.org> | 2020-02-20 13:17:27 +0100 |
|---|---|---|
| committer |   Thomas Gleixner <tglx@linutronix.de> | 2020-06-11 15:14:34 +0200 |
| commit | e9660391d0ebd174b169af3d6de680c2f836027c (patch) | |
| tree | 807efa70f0ff4dfaf303fe5d9d2358d2f93b4a3b /tools/perf/scripts/python/bin/flamegraph-record | |
| parent | x86/hw_breakpoint: Prevent data breakpoints on cpu_entry_area (diff) | |
x86/doublefault: Remove memmove() call
Use of memmove() in #DF is problematic considered tracing and other
instrumentation.
Remove the memmove() call and simply write out what needs doing; this
even clarifies the code, win-win! The code copies from the espfix64
stack to the normal task stack, there is no possible way for that to
overlap.
Survives selftests/x86, specifically sigreturn_64.
Suggested-by: Borislav Petkov <bp@alien8.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Alexandre Chartre <alexandre.chartre@oracle.com>
Acked-by: Andy Lutomirski <luto@kernel.org>
Link: https://lkml.kernel.org/r/20200505134058.863038566@linutronix.de
Diffstat (limited to 'tools/perf/scripts/python/bin/flamegraph-record')
0 files changed, 0 insertions, 0 deletions