From: Avi Kivity <avi@qumranet.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Agner Fog <agner@agner.org>,
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: Sun, 29 Jun 2008 15:31:54 +0300 [thread overview]
Message-ID: <486780BA.6010202@qumranet.com> (raw)
In-Reply-To: <48677E39.6000001@firstfloor.org>
Andi Kleen wrote:
> Avi Kivity wrote:
>
>
>> This is fixable.
>>
>
> Sure nearly everything is fixable, but why would you want to do that?
>
> For me the best fix currently seems to be to just not do that
> when it hurts.
>
>
We already use sse in the kernel (raid), presumably disabling preemption
there hurts some workloads.
With sse/avx gaining more features, we may see more requirements for
kernel fpu.
>> We could change kernel_fpu_begin() not to disable
>> preemption, but instead set a task flag. When we get the "no device"
>> fault, if the flag is set, save the fpu state into the kernel fpu save
>> area
>>
>
> What kernel fpu save area do you mean?
>
A new one, of course.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-06-29 12:32 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
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 [this message]
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=486780BA.6010202@qumranet.com \
--to=avi@qumranet.com \
--cc=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