From: Jeff Dike <jdike@addtoit.com>
To: Eli Cooper <elicooper@gmx.com>
Cc: Richard Weinberger <richard@nod.at>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] um: fix FPU register double-restore after sigreturn
Date: Fri, 18 Mar 2016 12:42:43 -0400 [thread overview]
Message-ID: <20160318164243.GA979@parts.user-mode-linux.org> (raw)
In-Reply-To: <56EC293B.8020407@gmx.com>
On Sat, Mar 19, 2016 at 12:13:47AM +0800, Eli Cooper wrote:
> I agree that we should keep userspace() minimal. So what in the first
> place is the FPU state save/restore code for? Or, what (except for
> sigreturn) could possibly mess the FPU state of the ptrace'd process
> without it?
My (vague) recollection was that with libc in there, I couldn't be
confident that it wouldn't unexpectedly use FP for something. So,
saving and restoring FP state was a hedge against that happening.
Jeff
--
Jeff Dike
AddToIt
978-254-0789 (o)
978-394-8986 (c)
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2016-03-18 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 1:25 [uml-devel] [PATCH] um: fix FPU register double-restore after sigreturn Eli Cooper
2016-03-17 22:21 ` Richard Weinberger
2016-03-18 1:41 ` Eli Cooper
2016-03-18 8:20 ` Richard Weinberger
2016-03-18 16:13 ` Eli Cooper
2016-03-18 16:42 ` Jeff Dike [this message]
2016-03-18 20:12 ` Richard Weinberger
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=20160318164243.GA979@parts.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=elicooper@gmx.com \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.