diff options
| author | Andy Lutomirski <luto@amacapital.net> | 2014-11-22 18:00:31 -0800 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2014-12-14 16:23:59 +0000 |
| commit | a6ac298db86a1add225ca7e655176bb5249f9a9d (patch) | |
| tree | 0528f854fed0a1ee8926946738376031a7ce872d /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 4c414592a79b82ddca76945c7afb4843684aa9a8 (diff) | |
x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C
commit af726f21ed8af2cdaa4e93098dc211521218ae65 upstream.
There's nothing special enough about the espfix64 double fault fixup to
justify writing it in assembly. Move it to C.
This also fixes a bug: if the double fault came from an IST stack, the
old asm code would return to a partially uninitialized stack frame.
Fixes: 3891a04aafd668686239349ea58f3314ea2af86b
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[bwh: Backported to 3.2:
- Keep using the paranoiderrorentry macro to generate the asm code
- Adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions