All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, KVM <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH][RFC] kvm-scheduler integration
Date: Mon, 09 Jul 2007 09:41:38 +0300	[thread overview]
Message-ID: <4691D8A2.2040706@qumranet.com> (raw)
In-Reply-To: <p73ir8uzpcx.fsf@bingen.suse.de>

[cc list restored]

Andi Kleen wrote:
> 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
>   

Yeah, I'll look into task_struct again to find a good place.

> Also it's a bit worrying to expose hooks into the scheduler
> to any modules. How would others be stopped from abusing this?
>   

The functions for installing a hook are out-of-line and
EXPORT_SYMBOL_GPL'ed, in case that helps.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Andi Kleen <andi-Vw/NltI1exuRpAAqCnN02g@public.gmane.org>
Cc: KVM <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH][RFC] kvm-scheduler integration
Date: Mon, 09 Jul 2007 09:41:38 +0300	[thread overview]
Message-ID: <4691D8A2.2040706@qumranet.com> (raw)
In-Reply-To: <p73ir8uzpcx.fsf-KvMlXPVkKihbpigZmTR7Iw@public.gmane.org>

[cc list restored]

Andi Kleen wrote:
> 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
>   

Yeah, I'll look into task_struct again to find a good place.

> Also it's a bit worrying to expose hooks into the scheduler
> to any modules. How would others be stopped from abusing this?
>   

The functions for installing a hook are out-of-line and
EXPORT_SYMBOL_GPL'ed, in case that helps.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
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/

  reply	other threads:[~2007-07-09  6:41 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 12:58 [PATCH][RFC] kvm-scheduler integration Avi Kivity
2007-07-08 12:58 ` Avi Kivity
2007-07-08 13:09 ` Ingo Molnar
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:35   ` Ingo Molnar
2007-07-08 13:41   ` Avi Kivity
2007-07-08 13:41     ` Avi Kivity
2007-07-08 13:48     ` Ingo Molnar
2007-07-08 13:48       ` Ingo Molnar
2007-07-08 13:53       ` Avi Kivity
2007-07-08 13:53         ` Avi Kivity
2007-07-08 13:59         ` Ingo Molnar
2007-07-08 13:59           ` Ingo Molnar
2007-07-08 15:13           ` Avi Kivity
2007-07-08 15:13             ` Avi Kivity
2007-07-10 11:18           ` Avi Kivity
2007-07-10 11:18             ` Avi Kivity
2007-07-10 11:30             ` Ingo Molnar
2007-07-10 11:30               ` Ingo Molnar
2007-07-08 23:32       ` [kvm-devel] " Rusty Russell
2007-07-08 23:32         ` Rusty Russell
2007-07-09  6:39         ` [kvm-devel] " Avi Kivity
2007-07-09  6:39           ` Avi Kivity
2007-07-10  1:09           ` [kvm-devel] " Rusty Russell
2007-07-10  1:09             ` Rusty Russell
2007-07-10  5:53             ` [kvm-devel] " Avi Kivity
2007-07-10  5:53               ` Avi Kivity
2007-07-10  6:47               ` [kvm-devel] " Rusty Russell
2007-07-10  6:47                 ` Rusty Russell
2007-07-10  7:19                 ` [kvm-devel] " Avi Kivity
2007-07-10  7:19                   ` Avi Kivity
2007-07-10  8:01                   ` [kvm-devel] " Rusty Russell
2007-07-10  8:01                     ` Rusty Russell
2007-07-10  8:24                     ` [kvm-devel] " Avi Kivity
2007-07-10  8:24                       ` Avi Kivity
2007-07-11  5:50                   ` [kvm-devel] " Avi Kivity
2007-07-11  5:50                     ` Avi Kivity
2007-07-08 19:07 ` Andi Kleen
2007-07-09  6:41   ` Avi Kivity [this message]
2007-07-09  6:41     ` Avi Kivity
2007-07-09  8:50 ` Shaohua Li
2007-07-09  8:50   ` Shaohua Li
2007-07-09  9:46   ` Avi Kivity
2007-07-09  9:46     ` Avi Kivity
2007-07-09 10:21     ` 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=4691D8A2.2040706@qumranet.com \
    --to=avi@qumranet.com \
    --cc=andi@firstfloor.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.