linux-kernel - Re: Revert "irq: Add tracepoint to softirq_raise"

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: <1299689179.15854.255.camel@gandalf.stny.rr.com>
Date:	Wed, 09 Mar 2011 11:46:19 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	monstr@...str.eu
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: Revert "irq: Add tracepoint to softirq_raise" - microblaze
 build

On Wed, 2011-03-09 at 13:20 +0100, Michal Simek wrote:
> Hi Frederic,
> 
> I have compiled ftrace support for Microblaze and I have reached a compilation failure.
> 
> I bisected it and I found that
> "irq: Add tracepoint to softirq_raise"
> (sha1:2bf2160d8805de64308e2e7c3cd97813cb58ed2f)
> caused it.
> 
> I also found one thread which could be related.
> http://kerneltrap.org/mailarchive/linux-kernel/2010/9/8/4616941
> 
> It is likely any missing header or so.
> 
> Do you know what can be wrong?
> 
> Thanks,
> Michal
> 
> 
> [ALL  ]   CC      kernel/trace/power-traces.o
> [ALL  ] In file included from 
> /mnt/projects/petalinux-v1.00-devel/software/linux-2.6.x/arch/microblaze/include/asm/irq.h:15,

Is there a reason that arch/microblaze/include/asm/irq.h includes
"linux/interrupt.h"?

-- Steve

> [ALL  ]                  from include/linux/irq.h:27,
> [ALL  ]                  from include/asm-generic/hardirq.h:12,
> [ALL  ]                  from 
> /mnt/projects/petalinux-v1.00-devel/software/linux-2.6.x/arch/microblaze/include/asm/hardirq.h:15,
> [ALL  ]                  from include/linux/hardirq.h:7,
> [ALL  ]                  from include/linux/ftrace_event.h:7,
> [ALL  ]                  from include/trace/ftrace.h:19,
> [ALL  ]                  from include/trace/define_trace.h:96,
> [ALL  ]                  from include/trace/events/power.h:240,
> [ALL  ]                  from kernel/trace/power-traces.c:14:
> [ALL  ] include/linux/interrupt.h: In function '__raise_softirq_irqoff':
> [ERROR] include/linux/interrupt.h:413: error: implicit declaration of function 'trace_softirq_raise'
> [ALL  ] In file included from include/trace/ftrace.h:554,
> [ALL  ]                  from include/trace/define_trace.h:96,
> [ALL  ]                  from include/trace/events/power.h:240,
> [ALL  ]                  from kernel/trace/power-traces.c:14:
> [ALL  ] include/trace/events/irq.h: In function 'ftrace_test_probe_irq_handler_entry':
> [ERROR] include/trace/events/irq.h:37: error: implicit declaration of function 
> 'check_trace_callback_type_irq_handler_entry'
> [ALL  ] include/trace/events/irq.h: In function 'ftrace_test_probe_irq_handler_exit':
> [ERROR] include/trace/events/irq.h:67: error: implicit declaration of function 
> 'check_trace_callback_type_irq_handler_exit'
> [ALL  ] include/trace/events/irq.h: In function 'ftrace_test_probe_softirq_entry':
> [ERROR] include/trace/events/irq.h:112: error: implicit declaration of function 
> 'check_trace_callback_type_softirq_entry'
> [ALL  ] include/trace/events/irq.h: In function 'ftrace_test_probe_softirq_exit':
> [ERROR] include/trace/events/irq.h:126: error: implicit declaration of function 
> 'check_trace_callback_type_softirq_exit'
> [ALL  ] include/trace/events/irq.h: In function 'ftrace_test_probe_softirq_raise':
> [ERROR] include/trace/events/irq.h:140: error: implicit declaration of function 
> 'check_trace_callback_type_softirq_raise'
> [ERROR] make[5]: *** [kernel/trace/power-traces.o] Error 1
> [ERROR] make[4]: *** [kernel/trace] Error 2
> [ERROR] make[3]: *** [kernel] Error 2
> 
> 


--
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/