From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
"K . Prasad" <prasad@linux.vnet.ibm.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: [PATCH 00/12] hw-breakpoints: new hardware breakpoints API
Date: Wed, 3 Jun 2009 00:43:24 +0200 [thread overview]
Message-ID: <1243982616-18212-1-git-send-email-fweisbec@gmail.com> (raw)
Hi Ingo,
The new hardware breakpoint API has benefit from deep reviews since
its first iteration several months ago, and Prasad has addressed
most (all?) of them.
After a small reorg and few fixes that were done recently, it seems
ready for integration on -tip.
I've tested it successfully for both kernel (ftrace) and user (gdb)
hardware breakpoints.
Thanks!
Frederic.
The following changes since commit 43bd1236234cacbc18d1476a9b57e7a306efddf5:
Frederic Weisbecker (1):
tracing/stat: remove unappropriate safe walk on list
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git hw-breakpoints
K.Prasad (12):
hw-breakpoints: prepare the code for Hardware Breakpoint interfaces
hw-breakpoints: introducing generic hardware breakpoint handler interfaces
hw-breakpoints: x86 architecture implementation of Hardware Breakpoint interfaces
hw-breakpoints: modifying generic debug exception to use thread-specific debug registers
hw-breakpoints: use wrapper routines around debug registers in processor related functions
hw-breakpoints: use the new wrapper routines to access debug registers in process/thread code
hw-breakpoints: modify signal handling code to refrain from re-enabling HW Breakpoints
hw-breakpoints: modify Ptrace routines to access breakpoint registers
hw-breakpoints: cleanup HW Breakpoint registers before kexec
hw-breakpoints: sample HW breakpoint over kernel data address
hw-breakpoints: ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces
hw-breakpoints: reset bits in dr6 after the corresponding exception is handled
arch/Kconfig | 4 +
arch/x86/Kconfig | 1 +
arch/x86/include/asm/a.out-core.h | 8 +-
arch/x86/include/asm/debugreg.h | 29 ++
arch/x86/include/asm/hw_breakpoint.h | 55 ++++
arch/x86/include/asm/processor.h | 8 +-
arch/x86/kernel/Makefile | 2 +-
arch/x86/kernel/hw_breakpoint.c | 391 +++++++++++++++++++++++
arch/x86/kernel/kgdb.c | 6 +
arch/x86/kernel/kprobes.c | 9 +-
arch/x86/kernel/machine_kexec_32.c | 2 +
arch/x86/kernel/machine_kexec_64.c | 2 +
arch/x86/kernel/process.c | 22 +-
arch/x86/kernel/process_32.c | 28 ++
arch/x86/kernel/process_64.c | 31 ++
arch/x86/kernel/ptrace.c | 231 +++++++++------
arch/x86/kernel/signal.c | 9 -
arch/x86/kernel/smpboot.c | 3 +
arch/x86/kernel/traps.c | 71 ++---
arch/x86/mm/kmmio.c | 8 +-
arch/x86/power/cpu_32.c | 13 +-
arch/x86/power/cpu_64.c | 12 +-
include/asm-generic/hw_breakpoint.h | 139 ++++++++
kernel/Makefile | 1 +
kernel/hw_breakpoint.c | 378 ++++++++++++++++++++++
kernel/trace/Kconfig | 21 ++
kernel/trace/Makefile | 1 +
kernel/trace/trace.h | 23 ++
kernel/trace/trace_ksym.c | 525 +++++++++++++++++++++++++++++++
kernel/trace/trace_selftest.c | 53 +++
samples/Kconfig | 6 +
samples/Makefile | 3 +-
samples/hw_breakpoint/Makefile | 1 +
samples/hw_breakpoint/data_breakpoint.c | 83 +++++
34 files changed, 1987 insertions(+), 192 deletions(-)
create mode 100644 arch/x86/include/asm/hw_breakpoint.h
create mode 100644 arch/x86/kernel/hw_breakpoint.c
create mode 100644 include/asm-generic/hw_breakpoint.h
create mode 100644 kernel/hw_breakpoint.c
create mode 100644 kernel/trace/trace_ksym.c
create mode 100644 samples/hw_breakpoint/Makefile
create mode 100644 samples/hw_breakpoint/data_breakpoint.c
next reply other threads:[~2009-06-02 22:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 22:43 Frederic Weisbecker [this message]
2009-06-02 22:43 ` [PATCH 01/12] hw-breakpoints: prepare the code for Hardware Breakpoint interfaces Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 02/12] hw-breakpoints: introducing generic hardware breakpoint handler interfaces Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 03/12] hw-breakpoints: x86 architecture implementation of Hardware Breakpoint interfaces Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 04/12] hw-breakpoints: modifying generic debug exception to use thread-specific debug registers Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 05/12] hw-breakpoints: use wrapper routines around debug registers in processor related functions Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 06/12] hw-breakpoints: use the new wrapper routines to access debug registers in process/thread code Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 07/12] hw-breakpoints: modify signal handling code to refrain from re-enabling HW Breakpoints Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 08/12] hw-breakpoints: modify Ptrace routines to access breakpoint registers Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 09/12] hw-breakpoints: cleanup HW Breakpoint registers before kexec Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 10/12] hw-breakpoints: sample HW breakpoint over kernel data address Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 11/12] hw-breakpoints: ftrace plugin for kernel symbol tracing using HW Breakpoint interfaces Frederic Weisbecker
2009-06-02 23:12 ` David Daney
2009-06-03 0:38 ` Frederic Weisbecker
2009-06-03 16:03 ` David Daney
2009-06-04 15:45 ` K.Prasad
2009-06-05 11:44 ` Frederic Weisbecker
2009-06-04 15:36 ` K.Prasad
2009-06-05 11:37 ` Frederic Weisbecker
2009-06-02 22:43 ` [PATCH 12/12] hw-breakpoints: reset bits in dr6 after the corresponding exception is handled Frederic Weisbecker
2009-06-02 23:38 ` [PATCH 00/12] hw-breakpoints: new hardware breakpoints API Ingo Molnar
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=1243982616-18212-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.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
Powered by JetHome