All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: kvm-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	shaohua.li@intel.com, rusty@rustcorp.com.au,
	Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 1/3] SCHED: Generic hooks for trapping task preemption
Date: Wed, 25 Jul 2007 15:49:03 +0300	[thread overview]
Message-ID: <46A746BF.4060301@qumranet.com> (raw)
In-Reply-To: <11853673871109-git-send-email-avi@qumranet.com>

Avi Kivity wrote:
>  /**
>   * prepare_task_switch - prepare to switch tasks
>   * @rq: the runqueue preparing to switch
> @@ -1687,6 +1746,7 @@ void fastcall wake_up_new_task(struct task_struct *p, unsigned long clone_flags)
>   */
>  static inline void prepare_task_switch(struct rq *rq, struct task_struct *next)
>  {
> +	fire_sched_out_preempt_hooks(current);
>   

This wants an extra arg, 'next', of course.

-- 
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: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Subject: Re: [PATCH 1/3] SCHED: Generic hooks for trapping task preemption
Date: Wed, 25 Jul 2007 15:49:03 +0300	[thread overview]
Message-ID: <46A746BF.4060301@qumranet.com> (raw)
In-Reply-To: <11853673871109-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
>  /**
>   * prepare_task_switch - prepare to switch tasks
>   * @rq: the runqueue preparing to switch
> @@ -1687,6 +1746,7 @@ void fastcall wake_up_new_task(struct task_struct *p, unsigned long clone_flags)
>   */
>  static inline void prepare_task_switch(struct rq *rq, struct task_struct *next)
>  {
> +	fire_sched_out_preempt_hooks(current);
>   

This wants an extra arg, 'next', of course.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  reply	other threads:[~2007-07-25 12:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 12:43 [PATCH 0/3] Scheduler preemption hooks, #2 Avi Kivity
2007-07-25 12:43 ` Avi Kivity
2007-07-25 12:43 ` [PATCH 1/3] SCHED: Generic hooks for trapping task preemption Avi Kivity
2007-07-25 12:43   ` Avi Kivity
2007-07-25 12:49   ` Avi Kivity [this message]
2007-07-25 12:49     ` Avi Kivity
2007-07-25 12:49   ` Ingo Molnar
2007-07-25 12:49     ` Ingo Molnar
2007-07-25 12:51     ` Avi Kivity
2007-07-25 12:52     ` Ingo Molnar
2007-07-25 13:13       ` Avi Kivity
2007-07-25 13:13         ` Avi Kivity
2007-07-25 13:03     ` Ingo Molnar
2007-07-25 12:43 ` [PATCH 2/3] KVM: Use the scheduler preemption hooks to make kvm preemptible Avi Kivity
2007-07-25 12:43   ` Avi Kivity
2007-07-25 12:43 ` [PATCH 3/3] KVM: Convert vm lock to a mutex Avi Kivity
2007-07-25 12: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=46A746BF.4060301@qumranet.com \
    --to=avi@qumranet.com \
    --cc=ak@suse.de \
    --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 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.