linux-kernel - Re: [sparc build bug] Re: [tip:perf/core] irq: Add tracepoint to softirq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CBD79CF.2060706@jp.fujitsu.com>
Date:	Tue, 19 Oct 2010 19:58:23 +0900
From:	Koki Sanagi <sanagi.koki@...fujitsu.com>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Ingo Molnar <mingo@...e.hu>, mathieu.desnoyers@...icios.com,
	fweisbec@...il.com, rostedt@...dmis.org, nhorman@...driver.com,
	scott.a.mcmillan@...el.com, tglx@...utronix.de,
	laijs@...fujitsu.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	eric.dumazet@...il.com, kaneshige.kenji@...fujitsu.com,
	davem@...emloft.net, izumi.taku@...fujitsu.com,
	kosaki.motohiro@...fujitsu.com, linux-tip-commits@...r.kernel.org,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	"Luck, Tony" <tony.luck@...el.com>
Subject: Re: [sparc build bug] Re: [tip:perf/core] irq: Add tracepoint to
 softirq_raise

(2010/10/18 19:48), Peter Zijlstra wrote:
> On Mon, 2010-10-18 at 11:44 +0200, Peter Zijlstra wrote:
>> On Wed, 2010-09-08 at 13:25 +0200, Ingo Molnar wrote:
>>> * tip-bot for Lai Jiangshan <laijs@...fujitsu.com> wrote:
>>>
>>>> Commit-ID:  2bf2160d8805de64308e2e7c3cd97813cb58ed2f
>>>> Gitweb:     http://git.kernel.org/tip/2bf2160d8805de64308e2e7c3cd97813cb58ed2f
>>>> Author:     Lai Jiangshan <laijs@...fujitsu.com>
>>>> AuthorDate: Mon, 23 Aug 2010 18:42:48 +0900
>>>> Committer:  Frederic Weisbecker <fweisbec@...il.com>
>>>> CommitDate: Tue, 7 Sep 2010 17:49:34 +0200
>>>>
>>>> irq: Add tracepoint to softirq_raise
>>>>
>>>> Add a tracepoint for tracing when softirq action is raised.
>>>>
>>>> This and the existing tracepoints complete softirq's tracepoints:
>>>> softirq_raise, softirq_entry and softirq_exit.
>>>>
>>>> And when this tracepoint is used in combination with
>>>> the softirq_entry tracepoint we can determine
>>>> the softirq raise latency.
>>>>
> 
>>> In file included from /home/mingo/tip/arch/sparc/include/asm/irq_32.h:11,
>>>                  from /home/mingo/tip/arch/sparc/include/asm/irq.h:6,
>>>                  from /home/mingo/tip/include/linux/irqnr.h:10,
>>>                  from /home/mingo/tip/include/linux/irq.h:22,
>>>                  from /home/mingo/tip/include/asm-generic/hardirq.h:6,
>>>                  from /home/mingo/tip/arch/sparc/include/asm/hardirq_32.h:11,
>>>                  from /home/mingo/tip/arch/sparc/include/asm/hardirq.h:6,
>>>                  from /home/mingo/tip/include/linux/hardirq.h:10,
>>>                  from /home/mingo/tip/include/linux/ftrace_event.h:7,
>>>                  from /home/mingo/tip/include/trace/syscall.h:6,
>>>                  from /home/mingo/tip/include/linux/syscalls.h:76,
>>>                  from /home/mingo/tip/init/initramfs.c:9:
>>> /home/mingo/tip/include/linux/interrupt.h: In function '__raise_softirq_irqoff':
>>> /home/mingo/tip/include/linux/interrupt.h:414: error: implicit declaration of function 'local_softirq_pending'
>>> /home/mingo/tip/include/linux/interrupt.h:414: error: lvalue required as left operand of assignment
>>> make[2]: *** [init/initramfs.o] Error 1
>>> make[2]: *** Waiting for unfinished jobs....
>>> In file included from /home/mingo/tip/arch/sparc/include/asm/irq_32.h:11,
>>
>> I could build sparc64_defconfig, but s390 is broken for me by this...
> 
> /me being very grumpy @ Lai.. ia64 is broken too!
> 
> /me goes revert this shite
> 

Now it is fixed.

http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=9f081ce5da2c8af297a0a7d15a57fb4beeed374b;hp=43e3bf203456c4f06bdd6060426976ad2bed9081

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/