From: Wang Nan <wangnan0@huawei.com>
To: <luto@amacapital.net>, <lizefan@huawei.com>
Cc: <mingo@kernel.org>, <masami.hiramatsu.pt@hitachi.com>,
<linux-kernel@vger.kernel.org>, <rostedt@goodmis.org>,
<linux-tip-commits@vger.kernel.org>, <tglx@linutronix.de>,
<hpa@zytor.com>, <dave.hansen@linux.intel.com>, <oleg@redhat.com>
Subject: [PATCH] x86, traps: early_trap_init() cleanup.
Date: Fri, 27 Feb 2015 11:28:50 +0800 [thread overview]
Message-ID: <1425007730-55260-1-git-send-email-wangnan0@huawei.com> (raw)
In-Reply-To: <CALCETrUy65TPqQEN8-_zOD_QVf0w=btPBXpFgho7G7t3tZ3V-w@mail.gmail.com>
As early_trap_init() doesn't use IST, replace set_intr_gate_ist(..., 0)
and set_system_intr_gate_ist(..., 0) with their standard counterparts.
set_intr_gate() requires a trace_debug symbol which we don't have and
won't use. Use a small macro trick as a workaround.
Signed-off-by: Wang Nan <wangnan0@huawei.com>
---
Hi Andy Lutomirski,
This patch is a bit tricky, but I think we don't need to define another
helper for such a small problem. What's your opinion?
Thank you!
---
arch/x86/kernel/traps.c | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index 4281988..c24434a 100644
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -925,17 +925,22 @@ dotraplinkage void do_iret_error(struct pt_regs *regs, long error_code)
/* Set of traps needed for early debugging. */
void __init early_trap_init(void)
{
+
/*
- * Don't set ist to DEBUG_STACK as it doesn't work until TSS is
- * ready in cpu_init() <-- trap_init(). Before trap_init(), CPU
- * runs at ring 0 so it is impossible to hit an invalid stack.
- * Using the original stack works well enough at this early
- * stage. DEBUG_STACK will be equipped after cpu_init() in
- * trap_init().
+ * Don't use IST to set DEBUG_STACK as it doesn't work until TSS is
+ * ready in cpu_init() <-- trap_init(). Before trap_init(), CPU runs at
+ * ring 0 so it is impossible to hit an invalid stack. Using the
+ * original stack works well enough at this early stage. DEBUG_STACK
+ * will be equipped after cpu_init() in trap_init().
+ *
+ * Since set_intr_gate() needs a trace_debug but we don't have it,
+ * use the following #define as a workaround.
*/
- set_intr_gate_ist(X86_TRAP_DB, &debug, 0);
+#define trace_debug debug
+ set_intr_gate(X86_TRAP_DB, debug);
+#undef trace_debug
/* int3 can be called from all */
- set_system_intr_gate_ist(X86_TRAP_BP, &int3, 0);
+ set_system_intr_gate(X86_TRAP_BP, &int3);
#ifdef CONFIG_X86_32
set_intr_gate(X86_TRAP_PF, page_fault);
#endif
@@ -1015,7 +1020,7 @@ void __init trap_init(void)
/*
* X86_TRAP_DB and X86_TRAP_BP have been set
- * in early_trap_init(). However, DEBUG_STACK works only after
+ * in early_trap_init(). However, ITS works only after
* cpu_init() loads TSS. See comments in early_trap_init().
*/
set_intr_gate_ist(X86_TRAP_DB, &debug, DEBUG_STACK);
--
1.8.4
next prev parent reply other threads:[~2015-02-27 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 5:49 [PATCH v2] x86, traps: Enable DEBUG_STACK after cpu_init() for TRAP_DB/BP Wang Nan
2015-02-26 13:12 ` [tip:x86/asm] x86/traps: " tip-bot for Wang Nan
2015-02-26 15:12 ` Andy Lutomirski
2015-02-27 2:21 ` Wang Nan
2015-02-27 2:33 ` Andy Lutomirski
2015-02-27 3:28 ` Wang Nan [this message]
2015-02-27 10:11 ` [PATCH] x86, traps: early_trap_init() cleanup Borislav Petkov
2015-02-27 4:19 ` [PATCH v2] x86, traps: separate set_intr_gate() and cleanup early_trap_init() Wang Nan
2015-03-02 9:55 ` Wang Nan
2015-03-02 17:06 ` Andy Lutomirski
2015-03-04 23:51 ` [tip:x86/asm] x86/traps: Separate set_intr_gate() and clean up early_trap_init() tip-bot for Wang Nan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425007730-55260-1-git-send-email-wangnan0@huawei.com \
--to=wangnan0@huawei.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=luto@amacapital.net \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®