From: Daniel Jacobowitz <dan@debian.org>
To: Dominic Sweetman <dom@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: RFC: Revise n32 ptrace interface
Date: Fri, 30 Sep 2005 16:34:34 -0400 [thread overview]
Message-ID: <20050930203434.GA18321@nevyn.them.org> (raw)
In-Reply-To: <17213.38447.42728.297338@mips.com>
On Fri, Sep 30, 2005 at 08:46:55PM +0100, Dominic Sweetman wrote:
>
> Ralf Baechle (ralf@linux-mips.org) writes:
>
> > 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.
>
> This is true so far.
>
> But assuming that 64-bit processing becomes increasingly interesting
> (which seems certain) and that some kind of DSP support with extra
> registers remains attractive (which seems fairly likely)... well, I'd
> have said that any 64-bit MIPS CPU configured from now on is quite
> likely to have extra DSP registers.
>
> So while "you aren't going to need it" for a while, anyone thinking of
> doing a non-compatible change to ptrace might want to reserve some
> space for these registers.
In the future they should be added using PTRACE_GETDSPREGS, or
something similar. No one's designed that yet, so the first person to
need it gets to do it right.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-09-30 20:35 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 ` RFC: Revise n32 " Ralf Baechle
2005-09-30 19:46 ` Dominic Sweetman
2005-09-30 20:34 ` Daniel Jacobowitz [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=20050930203434.GA18321@nevyn.them.org \
--to=dan@debian.org \
--cc=dom@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.