From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/6] sched: Introduce the finish_arch_post_lock_switch() scheduler hook
Date: Mon, 27 Feb 2012 15:48:13 +0100 [thread overview]
Message-ID: <1330354093.11248.71.camel@twins> (raw)
In-Reply-To: <1327081352-13178-2-git-send-email-catalin.marinas@arm.com>
On Fri, 2012-01-20 at 17:42 +0000, Catalin Marinas wrote:
> This hook is called by the scheduler after rq->lock has been released
> and interrupts enabled. It will be used in subsequent patches on the ARM
> architecture.
>
> Reviewed-by: Will Deacon <will.deacon@arm.com>
> Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Ingo Molnar <mingo@elte.hu>
Acked-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
> kernel/sched/core.c | 1 +
> kernel/sched/sched.h | 3 +++
> 2 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index df00cb0..f1db6d8 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -1937,6 +1937,7 @@ static void finish_task_switch(struct rq *rq, struct task_struct *prev)
> local_irq_enable();
> #endif /* __ARCH_WANT_INTERRUPTS_ON_CTXSW */
> finish_lock_switch(rq, prev);
> + finish_arch_post_lock_switch();
> trace_sched_stat_sleeptime(current, rq->clock);
>
> fire_sched_in_preempt_notifiers(current);
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index 98c0c26..d72483d 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -692,6 +692,9 @@ static inline int task_running(struct rq *rq, struct task_struct *p)
> #ifndef finish_arch_switch
> # define finish_arch_switch(prev) do { } while (0)
> #endif
> +#ifndef finish_arch_post_lock_switch
> +# define finish_arch_post_lock_switch() do { } while (0)
> +#endif
>
> #ifndef __ARCH_WANT_UNLOCKED_CTXSW
> static inline void prepare_lock_switch(struct rq *rq, struct task_struct *next)
>
next prev parent reply other threads:[~2012-02-27 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 17:42 [PATCH v3 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition Catalin Marinas
2012-01-20 17:42 ` [PATCH v3 1/6] sched: Introduce the finish_arch_post_lock_switch() scheduler hook Catalin Marinas
2012-02-27 14:48 ` Peter Zijlstra [this message]
2012-01-20 17:42 ` [PATCH v3 2/6] ARM: Use TTBR1 instead of reserved context ID Catalin Marinas
2012-01-20 17:42 ` [PATCH v3 3/6] ARM: Allow ASID 0 to be allocated to tasks Catalin Marinas
2012-01-20 17:42 ` [PATCH v3 4/6] ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on ASID-capable CPUs Catalin Marinas
2012-01-20 17:42 ` [PATCH v3 5/6] ARM: Remove current_mm per-cpu variable Catalin Marinas
2012-01-20 17:42 ` [PATCH v3 6/6] ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on pre-ARMv6 CPUs Catalin Marinas
2012-01-23 9:15 ` [PATCH v3 0/6] ARM: Remove the __ARCH_WANT_INTERRUPTS_ON_CTXSW definition Peter Zijlstra
2012-01-23 9:26 ` Catalin Marinas
2012-01-23 9:47 ` Russell King - ARM Linux
2012-01-23 9:53 ` Catalin Marinas
2012-01-24 15:14 ` Will Deacon
2012-01-25 10:31 ` Marc Zyngier
2012-02-16 13:58 ` Peter Zijlstra
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=1330354093.11248.71.camel@twins \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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).