From: Wolfgang Mauerer <w...@linux-kernel.net>
The trace mark string for faults uses an address
element to notify about the location of the instruction
that caused the fault. "address" is a bit dubious in
this context because it can mean either faulting address
or IP address. Replacing "address" with "ip" also makes
the message more consistent with Linux' page_fault_entry
trace point.
Signed-off-by: Wolfgang Mauerer <wolfgang.maue...@siemens.com>
Signed-off-by: Jan Kiszka <jan.kis...@siemens.com>
---
ksrc/nucleus/pod.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/ksrc/nucleus/pod.c b/ksrc/nucleus/pod.c
index 21763d5..37d35f5 100644
--- a/ksrc/nucleus/pod.c
+++ b/ksrc/nucleus/pod.c
@@ -2511,7 +2511,7 @@ int xnpod_trap_fault(xnarch_fltinfo_t *fltinfo)
thread = xnpod_current_thread();
trace_mark(xn_nucleus, thread_fault,
- "thread %p thread_name %s address %lu type %d",
+ "thread %p thread_name %s ip %p type %d",
thread, xnthread_name(thread), xnarch_fault_pc(fltinfo),
xnarch_fault_trap(fltinfo));
--
1.6.4
_______________________________________________
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
