linux-toradex.git/kernel, branch v2.6.21.2

[PATCH] clocksource: fix resume logic

2007-05-23T21:32:48+00:00

We need to make sure that the clocksources are resumed, when timekeeping is
resumed.  The current resume logic does not guarantee this.

Add a resume function pointer to the clocksource struct, so clocksource
drivers which need to reinitialize the clocksource can provide a resume
function.

Add a resume function, which calls the maybe available clocksource resume
functions and resets the watchdog function, so a stable TSC can be used
accross suspend/resume.

Signed-off-by: Thomas Gleixner 
Cc: john stultz 
Cc: Andi Kleen 
Cc: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Wright

[PATCH] highres/dyntick: prevent xtime lock contention

2007-05-23T21:32:46+00:00

While the !highres/!dyntick code assigns the duty of the do_timer() call to
one specific CPU, this was dropped in the highres/dyntick part during
development.

Steven Rostedt discovered the xtime lock contention on highres/dyntick due
to several CPUs trying to update jiffies.

Add the single CPU assignement back.  In the dyntick case this needs to be
handled carefully, as the CPU which has the do_timer() duty must drop the
assignement and let it be grabbed by another CPU, which is active.
Otherwise the do_timer() calls would not happen during the long sleep.

Signed-off-by: Thomas Gleixner 
Acked-by: Ingo Molnar 
Cc: Steven Rostedt 
Acked-by: Mark Lord 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Wright

Allow reading tainted flag as user

2007-04-24T15:23:08+00:00

The commit 34f5a39899f3f3e815da64f48ddb72942d86c366 restricted reading
of the tainted value. The attached patch changes this back to a
write-only check and restores the read behaviour of older versions.

Signed-off-by: Bastian Blank 
Cc: Theodore Ts'o 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] fix kernel oops with badly formatted module option

2007-04-12T22:31:41+00:00

Catch malformed kernel parameter usage of "param = value".  Spaces are not
supported, but don't cause a kernel fault on such usage, just report an
error.

Signed-off-by: Randy Dunlap 
Acked-by: Larry Finger 
Acked-by: Rusty Russell 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

sched.c: Remove unused variable 'relative'

2007-04-07T17:18:33+00:00

Getting rid of the p->children printout in show_task() left behind an
unused variable.

Signed-off-by: Linus Torvalds

[PATCH] sched: get rid of p->children use in show_task()

2007-04-07T17:06:51+00:00

the p->parent PID printout gives us all the information about the
task tree that we need - the eldest_child()/older_sibling()/
younger_sibling() printouts are mostly historic and i do not
remember ever having used those fields. (IMO in fact they confuse
the SysRq-T output.) So remove them.

This code has sentimental value though, those fields and
printouts are one of the oldest ones still surviving from
Linux v0.95's kernel/sched.c:

        if (p->p_ysptr || p->p_osptr)
                printk("   Younger sib=%d, older sib=%d\n\r",
                        p->p_ysptr ? p->p_ysptr->pid : -1,
                        p->p_osptr ? p->p_osptr->pid : -1);
        else
                printk("\n\r");

written 15 years ago, in early 1992.

Signed-off-by: Ingo Molnar 
Signed-off-by: Linus 'snif' Torvalds

[PATCH] irq-devres: fix failure path of devm_request_irq()

2007-04-07T17:05:21+00:00

devres should be deallocated with devres_free() not kfree().  This bug
corrupts slab on IRQ request failure.  Fix it.

Signed-off-by: Tejun Heo 
Cc: Andrew Morton 
Cc: Greg KH 
Signed-off-by: Linus Torvalds

[PATCH] high-res timers: resume fix

2007-04-07T17:03:43+00:00

Soeren Sonnenburg reported that upon resume he is getting
this backtrace:

 [] smp_apic_timer_interrupt+0x57/0x90
 [] retrigger_next_event+0x0/0xb0
 [] apic_timer_interrupt+0x28/0x30
 [] retrigger_next_event+0x0/0xb0
 [] __kfifo_put+0x8/0x90
 [] on_each_cpu+0x35/0x60
 [] clock_was_set+0x18/0x20
 [] timekeeping_resume+0x7c/0xa0
 [] __sysdev_resume+0x11/0x80
 [] sysdev_resume+0x47/0x80
 [] device_power_up+0x5/0x10

it turns out that on resume we mistakenly re-enable interrupts too
early.  Do the timer retrigger only on the current CPU.

Signed-off-by: Ingo Molnar 
Acked-by: Thomas Gleixner 
Acked-by: Soeren Sonnenburg 
Signed-off-by: Linus Torvalds

[PATCH] fix jiffies clocksource inittime

2007-04-05T04:12:47+00:00

In debugging a problem w/ the -rt tree, I noticed that on systems that mark
the tsc as unstable before it is registered, the TSC would still be
selected and used for a short period of time.  Digging in it looks to be a
result of the mix of the clocksource list changes and my clocksource
initialization changes.

With the -rt tree, using a bad TSC, even for a short period of time can
results in a hang at boot.  I was not able to reproduce this hang w/
mainline, but I'm not completely certain that someone won't trip on it.

This patch resolves the issue by initializing the jiffies clocksource
earlier so a bad TSC won't get selected just because nothing else is yet
registered.

Signed-off-by: John Stultz 
Acked-by: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] swsusp: fix memory shrinker

2007-04-05T04:12:47+00:00

Fix a bug in the swsusp's memory shrinker that causes some systems using
highmem to refuse to suspend to disk if image_size is set above 1/2 of
available RAM.

Special thanks to Jiri Slaby for reporting the problem and assistance in
debugging it.

Signed-off-by: Rafael J. Wysocki 
Cc: Jiri Slaby 
Cc: Pavel Machek 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds