From: Agner Fog <agner@agner.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: ABI change for device drivers using future AVX instruction set
Date: Sat, 28 Jun 2008 17:09:19 +0200 [thread overview]
Message-ID: <4866541F.1060709@agner.org> (raw)
In-Reply-To: <87myl5pyqo.fsf@basil.nowhere.org>
Andi Kleen wrote:
>If a x86 device driver doesn't use the standard kernel interfaces for
saving/restoring extended state
> (kernel_fpu_begin/end) it will die.That is because Linux uses lazy
FPU saving by default and when the
>lazy FPU exception hits kernel code it will crash because that's not
allowed. And the standard interfaces
>are going to handle all extended state supported by the kernel. Full
XSAVE support should be there for
> 2.6.27.
Thank you Andi. Finally an exact and exhaustive answer. :-)
This info is not in the "Unreliable Guide To Hacking The Linux Kernel"
or anywhere else except deeply hidden in the archives of this mailing
list. I had to actually look into the source code of kernel_fpu_begin to
verify that it saves not only the FPU but also the XMM registers and
that it disables pre-emption.
You see why I want proper documentation? If this had been documented in
some reference that was easy to find, I wouldn't have needed to take
your time with all these questions...
Note: Please Cc: me of answers.
next prev parent reply other threads:[~2008-06-28 15:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 15:32 ABI change for device drivers using future AVX instruction set Agner Fog
2008-06-25 16:22 ` Arjan van de Ven
2008-06-25 19:54 ` Agner Fog
2008-06-25 20:09 ` Arjan van de Ven
2008-06-26 1:11 ` H. Peter Anvin
2008-06-27 11:31 ` Agner Fog
2008-06-27 14:22 ` Arjan van de Ven
2008-06-28 8:05 ` Agner Fog
2008-06-28 8:10 ` David Miller
2008-06-28 11:47 ` Andi Kleen
2008-06-28 15:09 ` Agner Fog [this message]
2008-06-28 15:44 ` Helge Hafting
2008-06-28 20:02 ` Andi Kleen
2008-06-29 11:33 ` Avi Kivity
2008-06-29 12:21 ` Andi Kleen
2008-06-29 12:31 ` Avi Kivity
2008-06-29 13:07 ` Andi Kleen
2008-06-29 13:18 ` Avi Kivity
2008-06-29 13:23 ` Andi Kleen
2008-06-29 13:29 ` Avi Kivity
2008-06-29 22:08 ` H. Peter Anvin
2008-06-29 12:29 ` Alan Cox
2008-07-01 15:30 ` Arjan van de Ven
2008-06-25 20:14 ` Alan Cox
2008-06-26 14:01 ` 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=4866541F.1060709@agner.org \
--to=agner@agner.org \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--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