From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
maneesh@linux.vnet.ibm.com, Roland McGrath <roland@redhat.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>
Subject: [Patch 07/12] Modify signal handling code to refrain from re-enabling HW Breakpoints
Date: Fri, 24 Apr 2009 11:47:52 +0530 [thread overview]
Message-ID: <20090424061752.GH23812@in.ibm.com> (raw)
In-Reply-To: 20090424055710.764502564@prasadkr_t60p.in.ibm.com
[-- Attachment #1: modify_signal_07 --]
[-- Type: text/plain, Size: 1084 bytes --]
From: Alan Stern <stern@rowland.harvard.edu>
This patch disables re-enabling of Hardware Breakpoint registers through
the signal handling code. This is now done during
hw_breakpoint_handler().
Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
---
arch/x86/kernel/signal.c | 9 ---------
1 file changed, 9 deletions(-)
Index: arch/x86/kernel/signal.c
===================================================================
--- arch/x86/kernel/signal.c.orig
+++ arch/x86/kernel/signal.c
@@ -799,15 +799,6 @@ static void do_signal(struct pt_regs *re
signr = get_signal_to_deliver(&info, &ka, regs, NULL);
if (signr > 0) {
- /*
- * Re-enable any watchpoints before delivering the
- * signal to user space. The processor register will
- * have been cleared if the watchpoint triggered
- * inside the kernel.
- */
- if (current->thread.debugreg7)
- set_debugreg(current->thread.debugreg7, 7);
-
/* Whee! Actually deliver the signal. */
if (handle_signal(signr, &info, &ka, oldset, regs) == 0) {
/*
next prev parent reply other threads:[~2009-04-24 6:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090424055710.764502564@prasadkr_t60p.in.ibm.com>
2009-04-24 6:14 ` [Patch 01/12] Prepare the code for Hardware Breakpoint interfaces K.Prasad
2009-04-24 6:15 ` [Patch 02/12] Introducing generic hardware breakpoint handler interfaces K.Prasad
2009-04-24 6:16 ` [Patch 03/12] x86 architecture implementation of Hardware Breakpoint interfaces K.Prasad
2009-04-24 6:17 ` [Patch 04/12] Modifying generic debug exception to use thread-specific debug registers K.Prasad
2009-04-24 6:17 ` [Patch 05/12] Use wrapper routines around debug registers in processor related functions K.Prasad
2009-04-24 6:17 ` [Patch 06/12] Use the new wrapper routines to access debug registers in process/thread code K.Prasad
2009-04-24 6:17 ` K.Prasad [this message]
2009-04-24 6:18 ` [Patch 08/12] Modify Ptrace routines to access breakpoint registers K.Prasad
2009-04-24 6:18 ` [Patch 09/12] Cleanup HW Breakpoint registers before kexec K.Prasad
2009-04-24 6:18 ` [Patch 10/12] Sample HW breakpoint over kernel data address K.Prasad
2009-04-24 6:18 ` [Patch 11/12] ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces - v3 K.Prasad
2009-04-24 7:21 ` Frederic Weisbecker
2009-04-24 9:13 ` K.Prasad
2009-04-24 20:57 ` Frederic Weisbecker
2009-04-24 6:19 ` [Patch 12/12] Reset bits in dr6 after the corresponding exception is handled K.Prasad
[not found] <20090511114422.133566343@prasadkr_t60p.in.ibm.com>
2009-05-11 11:53 ` [Patch 07/12] Modify signal handling code to refrain from re-enabling HW Breakpoints K.Prasad
[not found] <20090513160546.592373797@prasadkr_t60p.in.ibm.com>
2009-05-13 16:14 ` K.Prasad
[not found] <20090515105133.629980476@prasadkr_t60p.in.ibm.com>
2009-05-15 10:58 ` K.Prasad
2009-05-16 0:29 ` K.Prasad
[not found] <20090521095613.834622717@prasadkr_t60p.in.ibm.com>
2009-05-21 14:02 ` K.Prasad
[not found] <20090530103857.715014561@prasadkr_t60p.in.ibm.com>
2009-05-30 10:52 ` K.Prasad
[not found] <20090601180605.799735829@prasadkr_t60p.in.ibm.com>
2009-06-01 18:15 ` K.Prasad
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=20090424061752.GH23812@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@au1.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@linux.vnet.ibm.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stern@rowland.harvard.edu \
/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