From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Cc: Benjamin Herrenschmidt <benh@au1.ibm.com>,
shaggy@linux.vnet.ibm.com,
Frederic Weisbecker <fweisbec@gmail.com>,
David Gibson <dwg@au1.ibm.com>,
paulus@samba.org, Roland McGrath <roland@redhat.com>
Subject: [RFC Patch 0/1] [hw-bkpt BookE] hw-breakpoint interfaces for BookE - ver I
Date: Tue, 27 Apr 2010 22:10:29 +0530 [thread overview]
Message-ID: <20100427164029.GA8303@in.ibm.com> (raw)
Hi All,
Please find a patch that implements hardware-breakpoint interfaces for
BookE processors. The patches are under continuous development and are sent
to receive early comments. For the moment, they are (only) compile tested (with
ppc64e_defconfig), further testing will accompany the ongoing development.
A few notes about the patchset, as below:
- The patch is designed with reference to BookIII-E type processors
specification (having two DAC/DVC registers).
- Instruction breakpoint requests are not implemented through the generic
breakpoint interfaces. Such requests are still possible for user-space through
ptrace.
- Breakpoint exceptions are designed to 'trigger-after-execute', although the
processors raise the exception before instruction execution. To achieve this,
the causative insruction is single-stepped over and the breakpoint handler is
invoked in the ICMP exception handler.
- The patches are dependant on the recent submissions (not yet integrated into
mainline) that bring support for hw-breakpoint weight (patchset from Frederic
Weisbecker LKML ref:1271999639-23605-1-git-send-regression-fweisbec@gmail.com)
and PPC64 hw-breakpoint support (linuxppc-dev
ref:20100414034340.GA6571@in.ibm.com).
Here are a few items identified to work upon in the successive versions.
TO DO
------
- Modify ptrace requests to use the generic hw-breakpoint interfaces
(PTRACE_<GET><SET>_DEBUGREG, PTRACE_SETHWDEBUG)
- Explore intergration of BookE and BookS code intergration
(hw_breakpoint.c and hw_breakpoint_booke.c)
- Code clean-up and reduction.
Kindly let me know about comments/suggestions, if any.
Thank You,
K.Prasad
reply other threads:[~2010-04-27 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100427164029.GA8303@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=benh@au1.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=roland@redhat.com \
--cc=shaggy@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).