From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: RFC: Revise n32 ptrace interface
Date: Fri, 30 Sep 2005 01:05:50 +0100 [thread overview]
Message-ID: <20050930000550.GE3983@linux-mips.org> (raw)
In-Reply-To: <20050922182601.GA10829@nevyn.them.org>
On Thu, Sep 22, 2005 at 02:26:01PM -0400, Daniel Jacobowitz wrote:
> 1. We need to get at the 64-bit registers. I considered a number of
> different approaches for this and decided to just implement a 64-bit
> PTRACE_GETREGS instead of messing with PTRACE_PEEKUSR. It's much simpler
> this way. I didn't add one for the DSP registers; that can be handled
> separately when someone's working on debug support for them...
I quite deliberately did omit DSP support from 64-bit ptrace(2); there
is currently no MIPS64 processor with DSP support that I know of.
Ralf
next prev parent reply other threads:[~2005-09-30 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 18:26 RFC: Revise n32 ptrace interface Daniel Jacobowitz
2005-09-28 22:11 ` [PATCH] Revise MIPS64 " Daniel Jacobowitz
2005-09-30 0:13 ` Ralf Baechle
2005-09-30 0:05 ` Ralf Baechle [this message]
2005-09-30 19:46 ` RFC: Revise n32 " Dominic Sweetman
2005-09-30 20:34 ` Daniel Jacobowitz
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=20050930000550.GE3983@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dan@debian.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