From: David Daney <ddaney@avtrex.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Hardware watchpoint register support for mips-linux.
Date: Tue, 22 Apr 2008 03:25:00 -0000 [thread overview]
Message-ID: <480D1763.10601@avtrex.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0804212246070.16496@cliff.in.clinika.pl>
Maciej W. Rozycki wrote:
>
> Well done! -- something I have meant to do for years, but never come to.
> Out of curiousity -- does your kernel side support MIPS architecture style
> watchpoints only or does it work with the R4000-style watch registers as
> well? I recall having a discussion with Daniel about how to support both
> in a reasonably abstract way long ago. Either way thanks a lot, and I
> have an R4k machine handy, so I can see if I find some time to give it a
> shot.
>
Currently it only handles mips32 style watch registers. I have no
documentation on the R4000 style registers.
I do however have an SGI Indy w/ R4400 which /proc/cpuinfo reports as
having watch registers, but since there is a lack of documentation, I
could not try it.
My plan for supporting different watch register formats is to have a
format identifier that is read by GDB via PTRACE_GET_WATCH_REGS. The
rest of the information is a union of the known formats.
Currently it reports the number of registers and the active mask bits.
But if R4000 does not fit with the mips32 register layout, its registers
would be layed out in a different union member.
I hope that makes sense.
David Daney
next prev parent reply other threads:[~2008-04-21 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 19:46 David Daney
2008-04-21 20:03 ` Daniel Jacobowitz
2008-04-21 20:34 ` David Daney
2008-04-21 21:14 ` Daniel Jacobowitz
2008-04-21 22:36 ` Maciej W. Rozycki
2008-04-22 3:25 ` David Daney [this message]
2008-04-22 20:27 ` Maciej W. Rozycki
2008-04-29 3:47 ` 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=480D1763.10601@avtrex.com \
--to=ddaney@avtrex.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@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