2006-09-26 16:52:29 +08:00
|
|
|
/*
|
|
|
|
|
* Save registers before calling assembly functions. This avoids
|
|
|
|
|
* disturbance of register allocation in some inline assembly constructs.
|
|
|
|
|
* Copyright 2001,2002 by Andi Kleen, SuSE Labs.
|
2008-05-13 03:20:42 +08:00
|
|
|
* Added trace_hardirqs callers - Copyright 2007 Steven Rostedt, Red Hat, Inc.
|
2006-09-26 16:52:29 +08:00
|
|
|
* Subject to the GNU public license, v.2. No warranty of any kind.
|
|
|
|
|
*/
|
2011-06-01 04:21:54 +08:00
|
|
|
#include <linux/linkage.h>
|
|
|
|
|
#include <asm/calling.h>
|
2014-04-17 16:17:26 +08:00
|
|
|
#include <asm/asm.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2011-06-01 04:21:54 +08:00
|
|
|
/* rdi: arg1 ... normal C conventions. rax is saved/restored. */
|
|
|
|
|
.macro THUNK name, func, put_ret_addr_in_rdi=0
|
2008-05-13 03:20:42 +08:00
|
|
|
.globl \name
|
|
|
|
|
\name:
|
2011-06-01 04:21:54 +08:00
|
|
|
|
|
|
|
|
/* this one pushes 9 elems, the next one would be %rIP */
|
x86/debug: Remove perpetually broken, unmaintainable dwarf annotations
So the dwarf2 annotations in low level assembly code have
become an increasing hindrance: unreadable, messy macros
mixed into some of the most security sensitive code paths
of the Linux kernel.
These debug info annotations don't even buy the upstream
kernel anything: dwarf driven stack unwinding has caused
problems in the past so it's out of tree, and the upstream
kernel only uses the much more robust framepointers based
stack unwinding method.
In addition to that there's a steady, slow bitrot going
on with these annotations, requiring frequent fixups.
There's no tooling and no functionality upstream that
keeps it correct.
So burn down the sick forest, allowing new, healthier growth:
27 files changed, 350 insertions(+), 1101 deletions(-)
Someone who has the willingness and time to do this
properly can attempt to reintroduce dwarf debuginfo in x86
assembly code plus dwarf unwinding from first principles,
with the following conditions:
- it should be maximally readable, and maximally low-key to
'ordinary' code reading and maintenance.
- find a build time method to insert dwarf annotations
automatically in the most common cases, for pop/push
instructions that manipulate the stack pointer. This could
be done for example via a preprocessing step that just
looks for common patterns - plus special annotations for
the few cases where we want to depart from the default.
We have hundreds of CFI annotations, so automating most of
that makes sense.
- it should come with build tooling checks that ensure that
CFI annotations are sensible. We've seen such efforts from
the framepointer side, and there's no reason it couldn't be
done on the dwarf side.
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Jan Beulich <JBeulich@suse.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-05-28 18:21:47 +08:00
|
|
|
pushq %rdi
|
|
|
|
|
pushq %rsi
|
|
|
|
|
pushq %rdx
|
|
|
|
|
pushq %rcx
|
|
|
|
|
pushq %rax
|
|
|
|
|
pushq %r8
|
|
|
|
|
pushq %r9
|
|
|
|
|
pushq %r10
|
|
|
|
|
pushq %r11
|
2011-06-01 04:21:54 +08:00
|
|
|
|
|
|
|
|
.if \put_ret_addr_in_rdi
|
2015-02-27 06:40:24 +08:00
|
|
|
/* 9*8(%rsp) is return addr on stack */
|
x86/debug: Remove perpetually broken, unmaintainable dwarf annotations
So the dwarf2 annotations in low level assembly code have
become an increasing hindrance: unreadable, messy macros
mixed into some of the most security sensitive code paths
of the Linux kernel.
These debug info annotations don't even buy the upstream
kernel anything: dwarf driven stack unwinding has caused
problems in the past so it's out of tree, and the upstream
kernel only uses the much more robust framepointers based
stack unwinding method.
In addition to that there's a steady, slow bitrot going
on with these annotations, requiring frequent fixups.
There's no tooling and no functionality upstream that
keeps it correct.
So burn down the sick forest, allowing new, healthier growth:
27 files changed, 350 insertions(+), 1101 deletions(-)
Someone who has the willingness and time to do this
properly can attempt to reintroduce dwarf debuginfo in x86
assembly code plus dwarf unwinding from first principles,
with the following conditions:
- it should be maximally readable, and maximally low-key to
'ordinary' code reading and maintenance.
- find a build time method to insert dwarf annotations
automatically in the most common cases, for pop/push
instructions that manipulate the stack pointer. This could
be done for example via a preprocessing step that just
looks for common patterns - plus special annotations for
the few cases where we want to depart from the default.
We have hundreds of CFI annotations, so automating most of
that makes sense.
- it should come with build tooling checks that ensure that
CFI annotations are sensible. We've seen such efforts from
the framepointer side, and there's no reason it couldn't be
done on the dwarf side.
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Jan Beulich <JBeulich@suse.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-05-28 18:21:47 +08:00
|
|
|
movq 9*8(%rsp), %rdi
|
2011-06-01 04:21:54 +08:00
|
|
|
.endif
|
|
|
|
|
|
2008-05-13 03:20:42 +08:00
|
|
|
call \func
|
|
|
|
|
jmp restore
|
2014-04-17 16:17:26 +08:00
|
|
|
_ASM_NOKPROBE(\name)
|
2008-05-13 03:20:42 +08:00
|
|
|
.endm
|
|
|
|
|
|
2011-06-01 04:21:54 +08:00
|
|
|
#ifdef CONFIG_TRACE_IRQFLAGS
|
|
|
|
|
THUNK trace_hardirqs_on_thunk,trace_hardirqs_on_caller,1
|
|
|
|
|
THUNK trace_hardirqs_off_thunk,trace_hardirqs_off_caller,1
|
2006-07-03 15:24:45 +08:00
|
|
|
#endif
|
2007-10-12 04:11:12 +08:00
|
|
|
|
|
|
|
|
#ifdef CONFIG_DEBUG_LOCK_ALLOC
|
2011-06-01 04:21:54 +08:00
|
|
|
THUNK lockdep_sys_exit_thunk,lockdep_sys_exit
|
2007-10-12 04:11:12 +08:00
|
|
|
#endif
|
2011-06-01 04:21:54 +08:00
|
|
|
|
2014-09-22 02:41:53 +08:00
|
|
|
#ifdef CONFIG_PREEMPT
|
|
|
|
|
THUNK ___preempt_schedule, preempt_schedule
|
|
|
|
|
#ifdef CONFIG_CONTEXT_TRACKING
|
|
|
|
|
THUNK ___preempt_schedule_context, preempt_schedule_context
|
|
|
|
|
#endif
|
|
|
|
|
#endif
|
|
|
|
|
|
2015-02-27 06:40:24 +08:00
|
|
|
#if defined(CONFIG_TRACE_IRQFLAGS) \
|
|
|
|
|
|| defined(CONFIG_DEBUG_LOCK_ALLOC) \
|
|
|
|
|
|| defined(CONFIG_PREEMPT)
|
2005-04-17 06:20:36 +08:00
|
|
|
restore:
|
x86/debug: Remove perpetually broken, unmaintainable dwarf annotations
So the dwarf2 annotations in low level assembly code have
become an increasing hindrance: unreadable, messy macros
mixed into some of the most security sensitive code paths
of the Linux kernel.
These debug info annotations don't even buy the upstream
kernel anything: dwarf driven stack unwinding has caused
problems in the past so it's out of tree, and the upstream
kernel only uses the much more robust framepointers based
stack unwinding method.
In addition to that there's a steady, slow bitrot going
on with these annotations, requiring frequent fixups.
There's no tooling and no functionality upstream that
keeps it correct.
So burn down the sick forest, allowing new, healthier growth:
27 files changed, 350 insertions(+), 1101 deletions(-)
Someone who has the willingness and time to do this
properly can attempt to reintroduce dwarf debuginfo in x86
assembly code plus dwarf unwinding from first principles,
with the following conditions:
- it should be maximally readable, and maximally low-key to
'ordinary' code reading and maintenance.
- find a build time method to insert dwarf annotations
automatically in the most common cases, for pop/push
instructions that manipulate the stack pointer. This could
be done for example via a preprocessing step that just
looks for common patterns - plus special annotations for
the few cases where we want to depart from the default.
We have hundreds of CFI annotations, so automating most of
that makes sense.
- it should come with build tooling checks that ensure that
CFI annotations are sensible. We've seen such efforts from
the framepointer side, and there's no reason it couldn't be
done on the dwarf side.
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Jan Beulich <JBeulich@suse.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-05-28 18:21:47 +08:00
|
|
|
popq %r11
|
|
|
|
|
popq %r10
|
|
|
|
|
popq %r9
|
|
|
|
|
popq %r8
|
|
|
|
|
popq %rax
|
|
|
|
|
popq %rcx
|
|
|
|
|
popq %rdx
|
|
|
|
|
popq %rsi
|
|
|
|
|
popq %rdi
|
2011-06-01 04:21:54 +08:00
|
|
|
ret
|
2014-04-17 16:17:26 +08:00
|
|
|
_ASM_NOKPROBE(restore)
|
2015-02-27 06:40:24 +08:00
|
|
|
#endif
|