From: Avi Kivity <avi@qumranet.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
shaohua.li@intel.com
Subject: Re: [PATCH 1/2] SCHED: Generic hooks for trapping task preemption
Date: Thu, 12 Jul 2007 08:48:02 +0300 [thread overview]
Message-ID: <4695C092.4070609@qumranet.com> (raw)
In-Reply-To: <1184217293.6005.754.camel@localhost.localdomain>
Rusty Russell wrote:
> On Wed, 2007-07-11 at 18:55 +0300, Avi Kivity wrote:
>
>> + fire_sched_out_preempt_hooks(current);
>> prepare_lock_switch(rq, next);
>> prepare_arch_switch(next);
>>
>
> Damn, I just found a use for this in lguest.
>
> Any chance of handing "next" to the sched_out hook so we can optimize
> the lguest <-> lguest switch?
>
> FYI, lguest turns off PGE globally when you load the module, because
> turning it off on each guest entry v. slow. With these hooks I can be
> far smarter...
>
Sure thang. Will be there in the next version.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-07-12 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:55 [PATCH 0/2][RFC] Scheduler preemption hooks, #2 Avi Kivity
2007-07-11 15:55 ` [PATCH 1/2] SCHED: Generic hooks for trapping task preemption Avi Kivity
2007-07-12 2:56 ` Rusty Russell
2007-07-12 5:14 ` Rusty Russell
2007-07-12 5:48 ` Avi Kivity [this message]
2007-07-11 15:55 ` [PATCH 2/2] KVM: Use the scheduler preemption hooks to make kvm preemptible Avi Kivity
2007-07-11 20:10 ` [kvm-devel] " Luca
2007-07-12 5:43 ` 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=4695C092.4070609@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 \
--cc=shaohua.li@intel.com \
/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