From: Gareth Hughes <gareth@precisioninsight.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Mark Kettenis <kettenis@wins.uva.nl>,
drepper@redhat.com
Cc: adam@yggdrasil.com, linux-kernel@vger.rutgers.edu,
bug-glibc@gnu.org, gdb@sourceware.cygnus.com
Subject: [PATCH] More updates to FXSR/SSE support in 2.4.0-test1
Date: Sun, 11 Jun 2000 01:03:00 -0000 [thread overview]
Message-ID: <394428DD.A2EFC21B@precisioninsight.com> (raw)
In-Reply-To: <E130wkg-0000uJ-00@the-village.bc.nu>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
Here's a copy of my latest work, this time kernel and glibc headers
only. I'm still working on updating GDB, as incorporating Mark's
suggestions leads to some problems with the stock 5.0 code (mainly in
the interpretation of the FPU tag word).
What are we doing now?
We use FXSAVE/FXRSTOR only to save and restore the FPU context as
before. Nice and fast. As always, the FPU state is only saved when the
FPU is used and restored with an #NM exception.
We (correctly) convert the FXSR-format data into the expanded signal
context, and include the original FXSR-format data like before. This
includes doing a full conversion between tag word formats.
We (correctly) convert the FXSR-format data on the
PTRACE_[GET|SET]FPREGS requests.
We just use the 512-byte FXSR data on PTRACE_[GET|SET]XFPREGS requests.
This requires updates to GDB, which I'm working on now. Nothing major,
the code is the same as in the kernel.
The tag word conversion originally seen in 2.4.0-test1 was almost
correct, but this code does a more thorough job - important for GDB 5.0
correctness.
As always, please let me know if you have any grievances. Doing the
conversion turned out to be a lot less ugly than I had imagined, and as
we only need to do it for signals, ptracing and dumping core, it doesn't
affect things too greatly. I will add in the core dumping support when
the work in this patch gets applied (in whatever form).
The signal handler test from my previous email will still work, and I
encourage you to verify this.
-- Gareth
patch-2.4.0test1-ac12-gth2.gz
patch-glibc-2.1.3-gth2.gz
[-- Attachment #2: patch-2.4.0test1-ac12-gth2.gz --]
[-- Type: application/x-gzip, Size: 4084 bytes --]
[-- Attachment #3: patch-glibc-2.1.3-gth2.gz --]
[-- Type: application/x-gzip, Size: 1453 bytes --]
next parent reply other threads:[~2000-06-11 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E130wkg-0000uJ-00@the-village.bc.nu>
2000-06-11 1:03 ` Gareth Hughes [this message]
[not found] ` <200006120002.e5C02mv14043@delius.kettenis.local>
2000-06-11 21:56 ` Gareth Hughes
2000-06-12 13:59 ` Mark Kettenis
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=394428DD.A2EFC21B@precisioninsight.com \
--to=gareth@precisioninsight.com \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bug-glibc@gnu.org \
--cc=drepper@redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
--cc=linux-kernel@vger.rutgers.edu \
/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