From: Peter Zijlstra <peterz@infradead.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, Kyle Huey <me@kylehuey.com>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Robert O'Callahan <rocallahan@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Fernandes <joel@joelfernandes.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2 7/8] x86/debug: Move cond_local_irq_enable() block into exc_debug_user()
Date: Fri, 21 Aug 2020 11:39:19 +0200 [thread overview]
Message-ID: <20200821102053.160728884@infradead.org> (raw)
In-Reply-To: 20200821093912.815135402@infradead.org
The cond_local_irq_enable() block, dealing with vm86 and sending
signals is only relevant for #DB-from-user, move it there.
This then reduces handle_debug() to only the notifier call, so rename
it to notify_debug().
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
arch/x86/kernel/traps.c | 51 +++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 26 deletions(-)
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -783,7 +783,8 @@ static __always_inline unsigned long deb
*
* May run on IST stack.
*/
-static bool handle_debug(struct pt_regs *regs, unsigned long *dr6)
+
+static bool notify_debug(struct pt_regs *regs, unsigned long *dr6)
{
struct task_struct *tsk = current;
@@ -793,31 +794,9 @@ static bool handle_debug(struct pt_regs
if (notify_die(DIE_DEBUG, "debug", regs, (long)dr6, 0, SIGTRAP) == NOTIFY_STOP)
return true;
- /* It's safe to allow irq's after DR6 has been saved */
- cond_local_irq_enable(regs);
-
- if (v8086_mode(regs)) {
- handle_vm86_trap((struct kernel_vm86_regs *) regs, 0,
- X86_TRAP_DB);
- goto out;
- }
-
- /*
- * Reload dr6, the notifier might have changed it.
- */
+ /* Reload the DR6 value, the notifier might have changed it */
*dr6 = tsk->thread.debugreg6;
- /*
- * If dr6 has no reason to give us about the origin of this trap,
- * then it's very likely the result of an icebp/int01 trap.
- * User wants a sigtrap for that.
- */
- if (*dr6 & (DR_STEP | DR_TRAP_BITS) || !*dr6)
- send_sigtrap(regs, 0, get_si_code(*dr6));
-
-out:
- cond_local_irq_disable(regs);
-
return false;
}
@@ -861,7 +840,7 @@ static __always_inline void exc_debug_ke
if (!dr6)
goto out;
- if (handle_debug(regs, &dr6))
+ if (notify_debug(regs, &dr6))
goto out;
if (WARN_ON_ONCE(dr6 & DR_STEP)) {
@@ -904,8 +883,28 @@ static __always_inline void exc_debug_us
irqentry_enter_from_user_mode(regs);
instrumentation_begin();
- handle_debug(regs, &dr6);
+ if (notify_debug(regs, &dr6))
+ goto out;
+
+ /* It's safe to allow irq's after DR6 has been saved */
+ local_irq_enable();
+
+ if (v8086_mode(regs)) {
+ handle_vm86_trap((struct kernel_vm86_regs *)regs, 0, X86_TRAP_DB);
+ goto out_irq;
+ }
+ /*
+ * If dr6 has no reason to give us about the origin of this trap,
+ * then it's very likely the result of an icebp/int01 trap.
+ * User wants a sigtrap for that.
+ */
+ if (dr6 & (DR_STEP | DR_TRAP_BITS) || !dr6)
+ send_sigtrap(regs, 0, get_si_code(dr6));
+
+out_irq:
+ local_irq_disable();
+out:
instrumentation_end();
irqentry_exit_to_user_mode(regs);
}
next prev parent reply other threads:[~2020-08-21 10:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 9:39 [PATCH v2 0/8] x86/debug: Untangle handle_debug() Peter Zijlstra
2020-08-21 9:39 ` [PATCH v2 1/8] x86/debug: Allow a single level of #DB recursion Peter Zijlstra
2020-08-21 9:39 ` [PATCH v2 2/8] x86/debug: Sync BTF earlier Peter Zijlstra
2020-08-23 23:03 ` Andy Lutomirski
2020-08-21 9:39 ` [PATCH v2 3/8] x86/debug: Move kprobe_debug_handler() into exc_debug_kernel() Peter Zijlstra
2020-08-23 23:01 ` Andy Lutomirski
2020-08-21 9:39 ` [PATCH v2 4/8] x86/debug: Remove handle_debug(.user) argument Peter Zijlstra
2020-08-23 23:05 ` Andy Lutomirski
2020-08-21 9:39 ` [PATCH v2 5/8] x86/debug: Simplify #DB signal code Peter Zijlstra
2020-08-23 23:09 ` Andy Lutomirski
2020-08-24 11:05 ` peterz
2020-08-24 11:26 ` Andrew Cooper
2020-08-24 12:00 ` peterz
2020-08-24 23:07 ` Andy Lutomirski
2020-08-24 23:09 ` Andy Lutomirski
2020-08-21 9:39 ` [PATCH v2 6/8] x86/debug: Move historical SYSENTER junk into exc_debug_kernel() Peter Zijlstra
2020-08-21 9:39 ` Peter Zijlstra [this message]
2020-08-21 9:39 ` [PATCH v2 8/8] x86/debug: Remove the historical junk Peter Zijlstra
2020-08-21 12:22 ` [PATCH v2.1 " peterz
2020-08-23 23:11 ` [PATCH v2 " Andy Lutomirski
2020-08-21 12:56 ` [PATCH v2 0/8] x86/debug: Untangle handle_debug() peterz
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=20200821102053.160728884@infradead.org \
--to=peterz@infradead.org \
--cc=alexandre.chartre@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brgerst@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=frederic@kernel.org \
--cc=jgross@suse.com \
--cc=joel@joelfernandes.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=me@kylehuey.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pmladek@suse.com \
--cc=rocallahan@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sean.j.christopherson@intel.com \
--cc=x86@kernel.org \
/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