From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch 0/6] MIPS: Hardware watch register support for gdb (version 3).
Date: Sat, 30 Aug 2008 01:37:05 -0700 [thread overview]
Message-ID: <48B906B1.3030708@avtrex.com> (raw)
In-Reply-To: <48B71ADD.601@avtrex.com>
David Daney wrote:
> Esteemed kernel hackers,
>
> To follow is my third pass at MIPS watch register support.
>
I think there will have to be at least one more pass at this.
The current design assumes that all debug registers support an identical
set of the I, R, and W bits and Mask.
However sections 8.23 and 8.24 of my
MIPS32® Architecture For Programmers
Volume III: The MIPS32® Privileged Resource Architecture
indicate that they do not have to uniform. I will have to augment the
ptrace structures to report the values for each register instead of a
single global value.
David Daney
prev parent reply other threads:[~2008-08-30 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 21:38 [Patch 0/6] MIPS: Hardware watch register support for gdb (version 3) David Daney
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 ` David Daney [this message]
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=48B906B1.3030708@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