From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] SCHED: Generic hooks for trapping task preemption
Date: Thu, 12 Jul 2007 15:14:53 +1000 [thread overview]
Message-ID: <1184217293.6005.754.camel@localhost.localdomain> (raw)
In-Reply-To: <11841693333159-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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...
Thanks!
Rusty.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-12 5:14 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
[not found] ` <11841693332609-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-11 15:55 ` [PATCH 1/2] SCHED: Generic hooks for trapping task preemption Avi Kivity
[not found] ` <11841693333159-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-12 2:56 ` Rusty Russell
2007-07-12 5:14 ` Rusty Russell [this message]
[not found] ` <1184217293.6005.754.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-12 5:48 ` Avi Kivity
2007-07-11 15:55 ` [PATCH 2/2] KVM: Use the scheduler preemption hooks to make kvm preemptible Avi Kivity
[not found] ` <1184169333786-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-11 20:10 ` Luca
[not found] ` <68676e00707111310v4862974am37dc7c723486b96c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=1184217293.6005.754.camel@localhost.localdomain \
--to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).