From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
Subject: [Patch 0/6] MIPS: Hardware watch register support for gdb (version 3).
Date: Thu, 28 Aug 2008 14:38:37 -0700 [thread overview]
Message-ID: <48B71ADD.601@avtrex.com> (raw)
Esteemed kernel hackers,
To follow is my third pass at MIPS watch register support.
This version has been tested on:
* MIPS 4KEc (mips32) with a single set of watch registers watchhi not
reporting I, R, and W conditions.
* MIPS 4KEc (mips32r2) with four sets of watch registers.
* R5000 SGI O2 (mips4 64bit) with no watch register support.
The patches are against 2.6.27-rc4
Changes from the previous version:
* Agreement from gdb maintainers that the ptrace interface is
workable.
* Work around for watchhi registers that do not report the I, R, and W
condition bits.
* General cleanup, including making much less code conditionally
compiled.
To really test the patch you will need a patched gdb. My current gdb
patch is here:
http://sourceware.org/ml/gdb-patches/2008-08/msg00650.html
If you have any comments or questions please let me know.
David Daney
next reply other threads:[~2008-08-28 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 21:38 David Daney [this message]
2008-08-28 21:45 ` Patch [1/6] MIPS: Add HARDWARE_WATCHPOINTS configure option David Daney
2008-08-28 21:55 ` [Patch 2/6] MIPS: Add HARDWARE_WATCHPOINTS definitions and support code David Daney
2008-08-28 22:02 ` [Patch 3/6] MIPS: Probe watch registers and report configuration David Daney
2008-08-28 22:07 ` [Patch 4/6] MIPS: Watch exception handling for HARDWARE_WATCHPOINTS David Daney
2008-08-28 22:11 ` [Patch 5/6] MIPS: Scheduler support " David Daney
2008-08-28 22:25 ` [Patch 6/6] MIPS: Ptrace " David Daney
2008-08-30 8:37 ` [Patch 0/6] MIPS: Hardware watch register support for gdb (version 3) David Daney
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=48B71ADD.601@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
/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