All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
	paulmck@linux.vnet.ibm.com
Subject: Re: [GIT PULL sched/core] cpu_stop: implement and use cpu_stop, take#3
Date: Sat, 8 May 2010 13:15:29 +0200	[thread overview]
Message-ID: <20100508111529.GA19796@elte.hu> (raw)
In-Reply-To: <1273164772-19149-1-git-send-email-tj@kernel.org>


* Tejun Heo <tj@kernel.org> wrote:

> Hello, Ingo.
> 
> Please pull from the following branch to receive cpu_stop patches.
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git cpu_stop
> 
> Adding mb()'s in synchronize_sched_expedited() is the only change
> since the last take[2].  Both Peter and Paul have acked the patchset.
> I'll post the patchset as replies to this message.
> 
> This patchset is on top of the current sched/core (99bd5e2f) and
> contains the following changes.
> 
> Paul E. McKenney (1):
>       scheduler: correctly place paranioa memory barriers in synchronize_sched_expedited()
> 
> Tejun Heo (4):
>       cpu_stop: implement stop_cpu[s]()
>       stop_machine: reimplement using cpu_stop
>       scheduler: replace migration_thread with cpu_stop
>       scheduler: kill paranoia check in synchronize_sched_expedited()
> 
>  Documentation/RCU/torture.txt |   10 -
>  arch/s390/kernel/time.c       |    1 -
>  drivers/xen/manage.c          |   14 +-
>  include/linux/rcutiny.h       |    2 -
>  include/linux/rcutree.h       |    1 -
>  include/linux/stop_machine.h  |   59 +++--
>  kernel/cpu.c                  |    8 -
>  kernel/module.c               |   14 +-
>  kernel/rcutorture.c           |    2 +-
>  kernel/sched.c                |  284 +++++-----------------
>  kernel/sched_fair.c           |   48 +++-
>  kernel/stop_machine.c         |  530 +++++++++++++++++++++++++++++++----------
>  12 files changed, 538 insertions(+), 435 deletions(-)

FYI, it doesnt build on x86 allnoconfig:

kernel/sched_fair.c: In function 'load_balance':
kernel/sched_fair.c:2917: error: implicit declaration of function 'stop_one_cpu_nowait'
kernel/sched.c: In function 'sched_exec':
kernel/sched.c:3084: error: implicit declaration of function 'stop_one_cpu'
kernel/sched.c: In function 'synchronize_sched_expedited':

	Ingo

  parent reply	other threads:[~2010-05-08 11:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 16:52 [GIT PULL sched/core] cpu_stop: implement and use cpu_stop, take#3 Tejun Heo
2010-05-06 16:52 ` [PATCH 1/5] cpu_stop: implement stop_cpu[s]() Tejun Heo
2010-05-06 16:52 ` [PATCH 2/5] stop_machine: reimplement using cpu_stop Tejun Heo
2010-05-11 21:50   ` Andrew Morton
2010-05-12  7:20     ` Tejun Heo
2010-05-06 16:52 ` [PATCH 3/5] sched: replace migration_thread with cpu_stop Tejun Heo
2010-05-06 19:29   ` Paul E. McKenney
2010-05-07  5:24     ` Tejun Heo
2010-05-06 16:52 ` [PATCH 4/5] sched: kill paranoia check in synchronize_sched_expedited() Tejun Heo
2010-05-06 16:52 ` [PATCH 5/5] sched: correctly place paranioa memory barriers " Tejun Heo
2010-05-08 11:15 ` Ingo Molnar [this message]
2010-05-08 12:47   ` [GIT PULL sched/core] cpu_stop: implement and use cpu_stop, take#3 Tejun Heo
2010-05-08 15:17   ` [PATCH] cpu_stop: add dummy implementation for UP Tejun Heo

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=20100508111529.GA19796@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tj@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.