@@ -10639,6 +10639,7 @@ static int trace_kho_notifier(struct notifier_block *self,
err |= fdt_begin_node(fdt, "ftrace");
err |= fdt_property(fdt, "compatible", compatible, sizeof(compatible));
err |= trace_kho_write_trace_array(fdt, &global_trace);
+ err |= trace_kho_write_events(fdt);
err |= fdt_end_node(fdt);
if (!err) {
@@ -12,6 +12,7 @@
#include <linux/sched/clock.h>
#include <linux/sched/mm.h>
#include <linux/idr.h>
+#include <linux/kexec.h>
#include "trace_output.h"
@@ -669,6 +670,33 @@ int trace_print_lat_context(struct trace_iterator *iter)
return !trace_seq_has_overflowed(s);
}
+int trace_kho_write_events(void *fdt)
+{
+#ifdef CONFIG_FTRACE_KHO
+ const char compatible[] = "ftrace,events-v1";
+ const char *name = "events";
+ struct trace_event *event;
+ unsigned key;
+ int err = 0;
+
+ err |= fdt_begin_node(fdt, name);
+ err |= fdt_property(fdt, "compatible", compatible, sizeof(compatible));
+
+ for (key = 0; key < EVENT_HASHSIZE; key++) {
+ hlist_for_each_entry(event, &event_hash[key], node)
+ err |= fdt_property(fdt, event->name, &event->type,
+ sizeof(event->type));
+ }
+
+ err |= fdt_end_node(fdt);
+
+ return err;
+#else
+ return 0;
+#endif
+}
+
+
/**
* ftrace_find_event - find a registered event
* @type: the type of event to look for
@@ -25,6 +25,7 @@ extern enum print_line_t print_event_fields(struct trace_iterator *iter,
extern void trace_event_read_lock(void);
extern void trace_event_read_unlock(void);
extern struct trace_event *ftrace_find_event(int type);
+extern int trace_kho_write_events(void *fdt);
extern enum print_line_t trace_nop_print(struct trace_iterator *iter,
int flags, struct trace_event *event);
Events and thus their parsing handle in ftrace have dynamic IDs that get assigned whenever the event is added to the system. If we want to parse trace events after kexec, we need to link event IDs back to the original trace event that existed before we kexec'ed. There are broadly 2 paths we could take for that: 1) Save full event description across KHO, restore after kexec, merge identical trace events into a single identifier. 2) Recover the ID of post-kexec added events so they get the same ID after kexec that they had before kexec This patch implements the second option. It's simpler and thus less intrusive. However, it means we can not fully parse affected events when the kernel removes or modifies trace events across a kho kexec. Signed-off-by: Alexander Graf <graf@amazon.com> --- kernel/trace/trace.c | 1 + kernel/trace/trace_output.c | 28 ++++++++++++++++++++++++++++ kernel/trace/trace_output.h | 1 + 3 files changed, 30 insertions(+)