From: Avi Kivity <avi@qumranet.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [PATCH][RFC] kvm-scheduler integration
Date: Wed, 11 Jul 2007 08:50:49 +0300 [thread overview]
Message-ID: <46946FB9.5040705@qumranet.com> (raw)
In-Reply-To: <469332F3.1000808@qumranet.com>
Avi Kivity wrote:
>
>> The
>> congruent case which comes to mind is lazy FPU handling.
>>
>
> That one has preempt_ops in hardware: cr0.ts and #NM.
However, that doesn't handle in-kernel use of the fpu.
kernel_fpu_begin()/kernel_fpu_end() could easily be modified to take
advantage of a generic preempt hook. I'll add a patch for that, and we
gain preemptible raid-5 parity calculation.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-07-11 6:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 12:58 [PATCH][RFC] kvm-scheduler integration Avi Kivity
2007-07-08 13:09 ` Ingo Molnar
2007-07-08 13:16 ` Avi Kivity
2007-07-08 13:36 ` Ingo Molnar
2007-07-08 13:35 ` Ingo Molnar
2007-07-08 13:41 ` Avi Kivity
2007-07-08 13:48 ` Ingo Molnar
2007-07-08 13:53 ` Avi Kivity
2007-07-08 13:59 ` Ingo Molnar
2007-07-08 15:13 ` Avi Kivity
2007-07-10 11:18 ` Avi Kivity
2007-07-10 11:30 ` Ingo Molnar
2007-07-08 23:32 ` [kvm-devel] " Rusty Russell
2007-07-09 6:39 ` Avi Kivity
2007-07-10 1:09 ` Rusty Russell
2007-07-10 5:53 ` Avi Kivity
2007-07-10 6:47 ` Rusty Russell
2007-07-10 7:19 ` Avi Kivity
2007-07-10 8:01 ` Rusty Russell
2007-07-10 8:24 ` Avi Kivity
2007-07-11 5:50 ` Avi Kivity [this message]
2007-07-08 19:07 ` Andi Kleen
2007-07-09 6:41 ` Avi Kivity
2007-07-09 8:50 ` Shaohua Li
2007-07-09 9:46 ` Avi Kivity
2007-07-09 10:21 ` 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=46946FB9.5040705@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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