From: Avi Kivity <avi@qumranet.com>
To: Andrea Arcangeli <andrea@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: fx_init schedule in atomic
Date: Fri, 02 May 2008 12:28:32 +0300 [thread overview]
Message-ID: <481ADEC0.60602@qumranet.com> (raw)
In-Reply-To: <20080501164333.GJ8150@duo.random>
Andrea Arcangeli wrote:
> This make sure not to schedule in atomic during fx_init. I also
> changed the name of fpu_init to fx_finit to avoid duplicating the name
> with fpu_init that is already used in the kernel, this makes grep
> simpler if nothing else.
>
>
Applied, thanks. Dynamic allocation for the fpu state was introduced in
2.6.26-rc, right?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-02 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 16:43 fx_init schedule in atomic Andrea Arcangeli
2008-05-02 9:28 ` Avi Kivity [this message]
2008-05-02 15:19 ` Andrea Arcangeli
2008-05-04 13:03 ` Avi Kivity
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=481ADEC0.60602@qumranet.com \
--to=avi@qumranet.com \
--cc=andrea@qumranet.com \
--cc=kvm-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox