[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1330079527-30711-1-git-send-email-mjw@redhat.com>
Date: Fri, 24 Feb 2012 11:32:05 +0100
From: "Mark J. Wielaard" <mjw@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Mark Wielaard <mjw@...hat.com>,
Thomas Gleixner <tglx@...utronix.de> (maintainer:X86
ARCHITECTURE...),
Ingo Molnar <mingo@...hat.com> (maintainer:X86 ARCHITECTURE...
,commit_signer:11/25=44%),
"H. Peter Anvin" <hpa@...or.com> (maintainer:X86 ARCHITECTURE...
,commit_signer:4/25=16%),
x86@...nel.org (maintainer:X86 ARCHITECTURE...),
Jan Beulich <jbeulich@...e.com> (commit_signer:6/25=24%),
Andi Kleen <ak@...ux.intel.com> (commit_signer:5/25=20%),
Frederic Weisbecker <fweisbec@...il.com> (commit_signer:4/25=16%)
Subject: [PATCH] x86-64: Fix CFI data for common_interrupt
From: Mark Wielaard <mjw@...hat.com>
Commit eab9e6 "x86-64: Fix CFI data for interrupt frames" introduced
a DW_CFA_def_cfa_expression in the SAVE_ARGS_IRQ macro. To later define
the CFA using a simple register+offset rule both register and offset
need to be supplied. Just using CFI_DEF_CFA_REGISTER leaves the offset
undefined. So use CFI_DEF_CFA with reg+off explicitly at the end of
common_interrupt.
Signed-off-by: Mark Wielaard <mjw@...hat.com>
Acked-by: Jan Beulich <jbeulich@...e.com>
---
arch/x86/kernel/entry_64.S | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
index 3fe8239..54be36b 100644
--- a/arch/x86/kernel/entry_64.S
+++ b/arch/x86/kernel/entry_64.S
@@ -813,7 +813,7 @@ ret_from_intr:
/* Restore saved previous stack */
popq %rsi
- CFI_DEF_CFA_REGISTER rsi
+ CFI_DEF_CFA rsi,SS+8-RBP /* reg/off reset after def_cfa_expr */
leaq ARGOFFSET-RBP(%rsi), %rsp
CFI_DEF_CFA_REGISTER rsp
CFI_ADJUST_CFA_OFFSET RBP-ARGOFFSET
--
1.7.7.6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists