From: Andi Kleen <andi@firstfloor.org>
To: avi@qumranet.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] kvm-scheduler integration
Date: 08 Jul 2007 21:07:10 +0200 [thread overview]
Message-ID: <p73ir8uzpcx.fsf@bingen.suse.de> (raw)
In-Reply-To: <11838994974161-git-send-email-avi@qumranet.com>
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> writes:
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 693f0e6..b705876 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -875,6 +875,10 @@ struct task_struct {
> pid_t pid;
> pid_t tgid;
>
> +#ifdef CONFIG_SCHED_KVM
> + struct kvm_vcpu *kvm_vcpu;
> +#endif
You should be careful to put this into a cache line that
is already touched during context switch. Otherwise
if it needs an additional cache miss it might become
very costly
Also it's a bit worrying to expose hooks into the scheduler
to any modules. How would others be stopped from abusing this?
-Andi
next prev parent reply other threads:[~2007-07-08 18:12 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
2007-07-08 19:07 ` Andi Kleen [this message]
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=p73ir8uzpcx.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=avi@qumranet.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