[PATCH] Tracing/Profiling: Ftrace: exported additional symbols after de7b2973 change

[Ron Rechenmacher]

After change to use "struct pointer instead of name hash",
additional symbols need to be exported using the EXPORT_TRACEPOINT_SYMBOL_GPL
macro.

Signed-off-by: Ron Rechenmacher <ron@xxxxxxxx>
---
 kernel/irq/handle.c               |    3 +++
 kernel/softirq.c                  |    3 +++
 kernel/trace/trace_sched_switch.c |    2 ++
 kernel/trace/trace_syscalls.c     |    3 +++
 4 files changed, 11 insertions(+), 0 deletions(-)

diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
index 6354802..241e165 100644
--- a/kernel/irq/handle.c
+++ b/kernel/irq/handle.c
@@ -195,3 +195,6 @@ irqreturn_t handle_irq_event(struct irq_desc *desc)
        irqd_clear(&desc->irq_data, IRQD_IRQ_INPROGRESS);
        return ret;
 }
+
+EXPORT_TRACEPOINT_SYMBOL_GPL(irq_handler_entry);
+EXPORT_TRACEPOINT_SYMBOL_GPL(irq_handler_exit);
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 479e443..adce531 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -785,3 +785,6 @@ unsigned int __weak arch_dynirq_lower_bound(unsigned int from)
 {
        return from;
 }
+
+EXPORT_TRACEPOINT_SYMBOL_GPL(softirq_entry);
+EXPORT_TRACEPOINT_SYMBOL_GPL(softirq_exit);
diff --git a/kernel/trace/trace_sched_switch.c b/kernel/trace/trace_sched_switch.c
index 419ca37..c5b96d2 100644
--- a/kernel/trace/trace_sched_switch.c
+++ b/kernel/trace/trace_sched_switch.c
@@ -99,3 +99,5 @@ void tracing_stop_cmdline_record(void)
 {
        tracing_stop_sched_switch();
 }
+
+EXPORT_TRACEPOINT_SYMBOL_GPL(sched_switch);
diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
index f97f6e3..377c712 100644
--- a/kernel/trace/trace_syscalls.c
+++ b/kernel/trace/trace_syscalls.c
@@ -748,3 +748,6 @@ static int syscall_exit_register(struct ftrace_event_call *event,
        }
        return 0;
 }
+
+EXPORT_TRACEPOINT_SYMBOL_GPL(sys_exit);
+EXPORT_TRACEPOINT_SYMBOL_GPL(sys_enter);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/