Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb ml <gdb@sourceware.org>
Cc: "Luis Machado" <luisgpm@linux.vnet.ibm.com>,
	"Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Subject: support for BookE hardware debug features
Date: Mon, 02 Mar 2009 20:39:00 -0000	[thread overview]
Message-ID: <1236026362.8949.96.camel@localhost.localdomain> (raw)

Hi folks,

This is a heads up message to mention some work we're doing to support
more BookE hardware debug features for userspace debugging under Linux,
which we intend to submit upstream. Perhaps someone out there has input
on this, or even want to help us. :-)

Right now GDB just supports one hardware watchpoint in embedded ppc
processors. We're adding support for:

- one more hardware watchpoint,
- four hardware breakpoints,
- support for the two DVCs (Data Value Compare), which enable
hardware-accelerated conditions for hardware watchpoints,
- two ranged hardware breakpoints,
- one ranged hardware watchpoint.

We're also working on the kernel side of the equation. We'll test it all
on the ppc440 processor.

We don't know yet how we'll extend gdb commands to express the ranged
breakpoints and watchpoints, and the DVCs. For the latter maybe we can
add some intelligence to use the registers if the condition expression
is simple enough, I didn't think much about this yet.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


             reply	other threads:[~2009-03-02 20:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 20:39 Thiago Jung Bauermann [this message]
2009-03-02 20:55 ` Joel Brobecker
2009-03-03 19:32   ` Thiago Jung Bauermann
2009-03-03 21:33     ` Joel Brobecker
2009-05-24 19:39 ` Thiago Jung Bauermann
2009-05-25 19:20   ` Sérgio Durigan Júnior
2009-05-26 14:28     ` Thiago Jung Bauermann

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=1236026362.8949.96.camel@localhost.localdomain \
    --to=bauerman@br.ibm.com \
    --cc=gdb@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=sergiodj@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