Re: 2.6.24-rc6-mm1: sparc64: undefined reference to `vmemmap_table'

2008-01-06 Thread Mariusz Kozlowski
Hello, This is from allnoconfig on sparc64: LD .tmp_vmlinux1 arch/sparc64/kernel/head.o: In function `kvmap_vmemmap': (.text+0x34ec): undefined reference to `vmemmap_table' arch/sparc64/kernel/head.o: In function `kvmap_vmemmap': (.text+0x34f4): undefined reference to

Re: [RFC PATCH 10/11] mcount tracer show task comm and pid

2008-01-06 Thread Ingo Molnar
* Mathieu Desnoyers [EMAIL PROTECTED] wrote: @@ -34,6 +34,7 @@ mctracer_add_trace_entry(struct mctracer { unsigned long idx, idx_next; struct mctracer_entry *entry; + struct task_struct *tsk = current; Aren't there situations, like in the middle of a context switch, where

gettimeofday not monotonous on sun4m

2008-01-06 Thread Martin Habets
Best wishes for 2008 to you all. I noticed the gettimeofday02 test from LTP fails as follows on both SS20 and SS10: gettimeofday020 INFO : checking if gettimeofday is monotonous, takes 30s gettimeofday021 FAIL : Time is going backwards: old 1197574068.852502 vs new

Re: 2.6.24-rc6-mm1: sparc64: undefined reference to `vmemmap_table'

2008-01-06 Thread David Miller
From: Andrew Morton [EMAIL PROTECTED] Date: Sun, 6 Jan 2008 02:15:54 -0800 On Sun, 6 Jan 2008 11:03:02 +0100 Mariusz Kozlowski [EMAIL PROTECTED] wrote: This is from allnoconfig on sparc64: LD .tmp_vmlinux1 arch/sparc64/kernel/head.o: In function `kvmap_vmemmap':

Re: [RFC PATCH 10/11] mcount tracer show task comm and pid

2008-01-06 Thread Mathieu Desnoyers
* Ingo Molnar ([EMAIL PROTECTED]) wrote: * Mathieu Desnoyers [EMAIL PROTECTED] wrote: @@ -34,6 +34,7 @@ mctracer_add_trace_entry(struct mctracer { unsigned long idx, idx_next; struct mctracer_entry *entry; + struct task_struct *tsk = current; Aren't there situations,

Re: [RFC PATCH 02/11] Add fastcall to do_IRQ for i386

2008-01-06 Thread H. Peter Anvin
Steven Rostedt wrote: On Thu, 3 Jan 2008, Mathieu Desnoyers wrote: I would propose to try to see how we can #ifdef two different __mcount assembly functions that would prepare the stack appropriately for each REGPARM cases. I have to confess that I've been testing this mostly on x86_64,