From: Paul Burton <paul.burton@imgtec.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
<gdb@sourceware.org>,
Matthew Fortune <matthew.fortune@imgtec.com>
Subject: Re: Adding MIPS registers (was Re: [PATCH v2] Reset errno before PTRACE_PEEKUSER for MIPS DSP_CONTROL)
Date: Wed, 10 Sep 2014 06:47:00 -0000 [thread overview]
Message-ID: <20140910064706.GS17248@pburton-laptop> (raw)
In-Reply-To: <20140909203922.GA27832@jhogan-linux.le.imgtec.org>
On Tue, Sep 09, 2014 at 09:39:22PM +0100, James Hogan wrote:
> > with the UFR
> > feature, so the register set presented will have to change dynamically,
> > according to that setting even for Linux targets.
>
> I have a feeling that UFR is currently unlikely to be enabled in Linux,
> due to subtleties with mode switches in multi-threaded processes
> requiring kernel support. Matthew or Paul (on CC) can probably confirm
> that.
Correct, UFR (along with UFE) is currently not enabled by Linux, and I'm
not aware of any need to deal with the pain involved in enabling it. There
is a need to switch mode across a whole process, which will need to be met
in some other way (the prctls in my internal branch, and hopefully the
same once upstream).
Paul
next prev parent reply other threads:[~2014-09-10 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1409608120-23991-1-git-send-email-james.hogan@imgtec.com>
[not found] ` <alpine.DEB.1.10.1409031340130.27075@tp.orcam.me.uk>
[not found] ` <20140903125111.GF12084@jhogan-linux.le.imgtec.org>
[not found] ` <alpine.DEB.1.10.1409031517450.27075@tp.orcam.me.uk>
2014-09-09 16:46 ` James Hogan
2014-09-09 17:57 ` Maciej W. Rozycki
2014-09-09 20:39 ` James Hogan
2014-09-10 6:47 ` Paul Burton [this message]
2014-09-10 7:44 ` Matthew Fortune
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=20140910064706.GS17248@pburton-laptop \
--to=paul.burton@imgtec.com \
--cc=gdb@sourceware.org \
--cc=james.hogan@imgtec.com \
--cc=macro@codesourcery.com \
--cc=matthew.fortune@imgtec.com \
/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