Tracepoints are named hierachially, and it makes more sense to keep a
general flow of information level from general to specific from left
to right, i.e.
x86_exceptions.page_fault_user|kernel
rather than
x86_exceptions.user|kernel_page_fault
Suggested-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Seiji Aguchi <seiji.aguchi@hds.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Link: http://lkml.kernel.org/r/20131111082955.GB12405@gmail.com
trace_irq_vector_regfunc, \
trace_irq_vector_unregfunc);
-DEFINE_PAGE_FAULT_EVENT(user_page_fault);
-DEFINE_PAGE_FAULT_EVENT(kernel_page_fault);
+DEFINE_PAGE_FAULT_EVENT(page_fault_user);
+DEFINE_PAGE_FAULT_EVENT(page_fault_kernel);
#undef TRACE_INCLUDE_PATH
#define TRACE_INCLUDE_PATH .
unsigned long error_code)
{
if (user_mode(regs))
- trace_user_page_fault(read_cr2(), regs, error_code);
+ trace_page_fault_user(read_cr2(), regs, error_code);
else
- trace_kernel_page_fault(read_cr2(), regs, error_code);
+ trace_page_fault_kernel(read_cr2(), regs, error_code);
}
dotraplinkage void __kprobes