From: Manfred Spraul <manfred@colorfullife.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Lazy FPU handling in ptrace
Date: Fri, 14 Mar 2003 22:11:53 +0100 [thread overview]
Message-ID: <3E724599.5050004@colorfullife.com> (raw)
Andi wrote:
>(untested, but obviously correct ;-)
>-Andi
>
Famous last words.
The patch is not needed: __switch_to unlazies the fpu state of the
previous thread. ptrace PTRACE_SETFPREGS and PTRACE_SETFPXREGS only
operate on stopped threads, thus it's guaranteed that the fpu state is
stored in the task structure.
--
Manfred
next reply other threads:[~2003-03-14 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 21:11 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 20:56 [PATCH] Lazy FPU handling in ptrace Andi Kleen
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=3E724599.5050004@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.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