From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: [Patch 0/6] MIPS Hardware watchpoint support for gdb (version 2).
Date: Mon, 28 Apr 2008 18:21:54 -0700 [thread overview]
Message-ID: <48167832.3090103@avtrex.com> (raw)
This is my second take at MIPS watch register support.
Changes from the previous version include:
* Change layout of structures used by ptrace to eliminate holes.
* Use [set|clear]_tsk_thread_flag() and friends instead of racy direct
access.
* mips64 support (untested).
* Fix sparse warnings.
For this version of the patch you will need the corresponding gdb patch
which can be found here:
http://sourceware.org/ml/gdb-patches/2008-04/msg00642.html
David Daney
next reply other threads:[~2008-04-29 1:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 1:21 David Daney [this message]
2008-04-29 1:29 ` [PATCH 1/6] Add HARDWARE_WATCHPOINTS configure option David Daney
2008-04-29 1:31 ` [PATCH 2/6] Add HARDWARE_WATCHPOINTS definitions and support code David Daney
2008-04-29 1:33 ` [PATCH 3/6] Probe watch registers and report configuration David Daney
2008-04-29 1:37 ` [PATCH 4/6] Watch exception handling for HARDWARE_WATCHPOINTS David Daney
2008-04-29 1:39 ` [PATCH 5/6] Scheduler support " David Daney
2008-04-29 1:43 ` [PATCH 6/6] Ptrace " 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=48167832.3090103@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