linux-toradex.git/kernel/kthread.c, branch imx-android-r10.4

cpuset: fix the problem that cpuset_mem_spread_node() returns an offline node

2010-03-24T23:31:21+00:00

cpuset_mem_spread_node() returns an offline node, and causes an oops.

This patch fixes it by initializing task->mems_allowed to
node_states[N_HIGH_MEMORY], and updating task->mems_allowed when doing
memory hotplug.

Signed-off-by: Miao Xie 
Acked-by: David Rientjes 
Reported-by: Nick Piggin 
Tested-by: Nick Piggin 
Cc: Paul Menage 
Cc: Li Zefan 
Cc: Ingo Molnar 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kthread, sched: Remove reference to kthread_create_on_cpu

2010-02-09T10:47:39+00:00

kthread_create_on_cpu doesn't exist so update a comment in
kthread.c to reflect this.

Signed-off-by: Anton Blanchard 
Acked-by: Rusty Russell 
Cc: Peter Zijlstra 
LKML-Reference: <20100209040740.GB3702@kryten>
Signed-off-by: Ingo Molnar

sched: Move kthread_bind() back to kthread.c

2009-12-16T18:01:57+00:00

Since kthread_bind() lost its dependencies on sched.c, move it
back where it came from.

Signed-off-by: Peter Zijlstra 
Cc: Mike Galbraith 
LKML-Reference: <20091216170518.039524041@chello.nl>
Signed-off-by: Ingo Molnar

sched: Fix kthread_bind() by moving the body of kthread_bind() to sched.c

2009-11-03T06:25:00+00:00

Eric Paris reported that commit
f685ceacab07d3f6c236f04803e2f2f0dbcc5afb causes boot time
PREEMPT_DEBUG complaints.

 [    4.590699] BUG: using smp_processor_id() in preemptible [00000000] code: rmmod/1314
 [    4.593043] caller is task_hot+0x86/0xd0

Since kthread_bind() messes with scheduler internals, move the
body to sched.c, and lock the runqueue.

Reported-by: Eric Paris 
Signed-off-by: Mike Galbraith 
Tested-by: Eric Paris 
Cc: Peter Zijlstra 
LKML-Reference: <1256813310.7574.3.camel@marge.simson.net>
[ v2: fix !SMP build and clean up ]
Signed-off-by: Ingo Molnar

sched: Keep kthreads at default priority

2009-09-09T15:30:06+00:00

Removes kthread/workqueue priority boost, they increase worst-case
desktop latencies.

Signed-off-by: Mike Galbraith 
Acked-by: Peter Zijlstra 
LKML-Reference: <1252486344.28645.18.camel@marge.simson.net>
Signed-off-by: Ingo Molnar

update the comment in kthread_stop()

2009-07-27T19:15:46+00:00

Commit 63706172f332fd3f6e7458ebfb35fa6de9c21dc5 ("kthreads: rework
kthread_stop()") removed the limitation that the thread function mysr
not call do_exit() itself, but forgot to update the comment.

Since that commit it is OK to use kthread_stop() even if kthread can
exit itself.

Signed-off-by: Oleg Nesterov 
Signed-off-by: Rusty Russell 
Signed-off-by: Linus Torvalds

kthreads: rework kthread_stop()

2009-06-18T20:03:54+00:00

Based on Eric's patch which in turn was based on my patch.

kthread_stop() has the nasty problems:

- it runs unpredictably long with the global semaphore held.

- it deadlocks if kthread itself does kthread_stop() before it obeys
  the kthread_should_stop() request.

- it is not useable if kthread exits on its own, see for example the
  ugly "wait_to_die:" hack in migration_thread()

- it is not possible to just tell kthread it should stop, we must always
  wait for its exit.

With this patch kthread() allocates all neccesary data (struct kthread) on
its own stack, globals kthread_stop_xxx are deleted.  ->vfork_done is used
as a pointer into "struct kthread", this means kthread_stop() can easily
wait for kthread's exit.

Signed-off-by: Oleg Nesterov 
Cc: Christoph Hellwig 
Cc: "Eric W. Biederman" 
Cc: Ingo Molnar 
Cc: Pavel Emelyanov 
Cc: Rusty Russell 
Cc: Vitaliy Gusev 
Signed-off-by: Linus Torvalds

kthreads: simplify the startup synchronization

2009-06-18T20:03:53+00:00

We use two completions two create the kernel thread, this is a bit ugly.
kthread() wakes up create_kthread() via ->started, then create_kthread()
wakes up the caller kthread_create() via ->done.  But kthread() does not
need to wait for kthread(), it can just return.  Instead kthread() itself
can wake up the caller of kthread_create().

Kill kthread_create_info->started, ->done is enough.  This improves the
scalability a bit and sijmplifies the code.

The only problem if kernel_thread() fails, in that case create_kthread()
must do complete(&create->done).

Signed-off-by: Oleg Nesterov 
Cc: Christoph Hellwig 
Cc: "Eric W. Biederman" 
Cc: Ingo Molnar 
Cc: Pavel Emelyanov 
Cc: Rusty Russell 
Cc: Vitaliy Gusev 
Signed-off-by: Linus Torvalds

cpuset,mm: update tasks' mems_allowed in time

2009-06-17T02:47:31+00:00

Fix allocating page cache/slab object on the unallowed node when memory
spread is set by updating tasks' mems_allowed after its cpuset's mems is
changed.

In order to update tasks' mems_allowed in time, we must modify the code of
memory policy.  Because the memory policy is applied in the process's
context originally.  After applying this patch, one task directly
manipulates anothers mems_allowed, and we use alloc_lock in the
task_struct to protect mems_allowed and memory policy of the task.

But in the fast path, we didn't use lock to protect them, because adding a
lock may lead to performance regression.  But if we don't add a lock,the
task might see no nodes when changing cpuset's mems_allowed to some
non-overlapping set.  In order to avoid it, we set all new allowed nodes,
then clear newly disallowed ones.

[lee.schermerhorn@hp.com:
  The rework of mpol_new() to extract the adjusting of the node mask to
  apply cpuset and mpol flags "context" breaks set_mempolicy() and mbind()
  with MPOL_PREFERRED and a NULL nodemask--i.e., explicit local
  allocation.  Fix this by adding the check for MPOL_PREFERRED and empty
  node mask to mpol_new_mpolicy().

  Remove the now unneeded 'nodes = NULL' from mpol_new().

  Note that mpol_new_mempolicy() is always called with a non-NULL
  'nodes' parameter now that it has been removed from mpol_new().
  Therefore, we don't need to test nodes for NULL before testing it for
  'empty'.  However, just to be extra paranoid, add a VM_BUG_ON() to
  verify this assumption.]
[lee.schermerhorn@hp.com:

  I don't think the function name 'mpol_new_mempolicy' is descriptive
  enough to differentiate it from mpol_new().

  This function applies cpuset set context, usually constraining nodes
  to those allowed by the cpuset.  However, when the 'RELATIVE_NODES flag
  is set, it also translates the nodes.  So I settled on
  'mpol_set_nodemask()', because the comment block for mpol_new() mentions
  that we need to call this function to "set nodes".

  Some additional minor line length, whitespace and typo cleanup.]
Signed-off-by: Miao Xie 
Cc: Ingo Molnar 
Cc: Peter Zijlstra 
Cc: Christoph Lameter 
Cc: Paul Menage 
Cc: Nick Piggin 
Cc: Yasunori Goto 
Cc: Pekka Enberg 
Cc: David Rientjes 
Signed-off-by: Lee Schermerhorn 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

tracing/events: move trace point headers into include/trace/events

2009-04-15T02:05:43+00:00

Impact: clean up

Create a sub directory in include/trace called events to keep the
trace point headers in their own separate directory. Only headers that
declare trace points should be defined in this directory.

Cc: Peter Zijlstra 
Cc: Thomas Gleixner 
Cc: Neil Horman 
Cc: Zhao Lei 
Cc: Eduard - Gabriel Munteanu 
Cc: Pekka Enberg 
Signed-off-by: Steven Rostedt