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: Re: support for BookE hardware debug features
Date: Sun, 24 May 2009 19:39:00 -0000 [thread overview]
Message-ID: <1243193918.10406.0.camel@hactar> (raw)
In-Reply-To: <1236026362.8949.96.camel@localhost.localdomain>
Hi all,
Em Seg, 2009-03-02 Ã s 17:39 -0300, Thiago Jung Bauermann escreveu:
> 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.
Just to give a status update on this work: up to now we have the
following features implemented and fully functional:
- one more hardware watchpoint,
- four hardware breakpoints,
- one ranged hardware watchpoint.
The above are working for both native GDB and gdbserver, both on Linux.
> We're also working on the kernel side of the equation. We'll test it all
> on the ppc440 processor.
The kernel support is going along nicely, but since it's not ready nor
accepted upstream yet, we can't start posting our GDB patches that are
ready.
> We don't know yet how we'll extend gdb commands to express the ranged
> breakpoints and watchpoints, and the DVCs.
I implemented a "watch-range" command, which takes a start address (or
expression which evaluates to an address) and an end address (or
expression). Not sure if I'll keep it that way or change. Didn't think
much about it yet.
Also, I want GDB to automagically use the ranged watchpoint for big
structs and arrays.
> 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.
We are just starting to work on the DVC (conditioned hw watchpoint), but
for now I'm inclined to use it automagically for simple expressions with
just one == or != operator. We're taking into account Joel's comments
and suggestions on this. Thanks Joel for your input!
Sérgio did most of the work here. I don't know if he wants to add
anything to this report...
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-05-24 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 20:39 Thiago Jung Bauermann
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 [this message]
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=1243193918.10406.0.camel@hactar \
--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