linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Matthew Fortune <Matthew.Fortune@imgtec.com>
Cc: James Hogan <James.Hogan@imgtec.com>,
	Bhushan Attarde <Bhushan.Attarde@imgtec.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Andrew Bennett <Andrew.Bennett@imgtec.com>,
	Jaydeep Patil <Jaydeep.Patil@imgtec.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: RE: [PATCH 02/24]     Add MIPS32 FPU64 GDB target descriptions
Date: Fri, 21 Oct 2016 20:24:44 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1610212020340.31859@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1610131614180.31859@tp.orcam.me.uk>

On Fri, 21 Oct 2016, Maciej W. Rozycki wrote:

>  If we had such a dedicated virtual $fre, and we decided sometime to let 
> the user actually write to it and switch the mode process-wide, then we 
> could simply invoke the right prctl(2) call in response to the user's 
> ptrace(2) request.

 Or we could call it $fp_mode and map it directly to prctl(PR_GET_FP_MODE) 
and prctl(PR_SET_FP_MODE, ...).

  Maciej

      reply	other threads:[~2016-10-21 19:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1467038991-6600-1-git-send-email-bhushan.attarde@imgtec.com>
     [not found] ` <1467038991-6600-2-git-send-email-bhushan.attarde@imgtec.com>
     [not found]   ` <alpine.DEB.2.00.1607221827040.4076@tp.orcam.me.uk>
     [not found]     ` <20161012135803.GT19354@jhogan-linux.le.imgtec.org>
2016-10-12 16:29       ` [PATCH 02/24] Add MIPS32 FPU64 GDB target descriptions Maciej W. Rozycki
2016-10-12 16:29         ` Maciej W. Rozycki
2016-10-12 18:05         ` James Hogan
2016-10-12 18:05           ` James Hogan
2016-10-12 22:04           ` Maciej W. Rozycki
2016-10-12 22:04             ` Maciej W. Rozycki
2016-10-12 22:26             ` James Hogan
2016-10-12 22:26               ` James Hogan
2016-10-13 10:09             ` Matthew Fortune
2016-10-21 19:16               ` Maciej W. Rozycki
2016-10-21 19:24                 ` Maciej W. Rozycki [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=alpine.DEB.2.00.1610212020340.31859@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=Andrew.Bennett@imgtec.com \
    --cc=Bhushan.Attarde@imgtec.com \
    --cc=James.Hogan@imgtec.com \
    --cc=Jaydeep.Patil@imgtec.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for NNTP newsgroup(s).