x86, mpx: trace allocations of new bounds tables
From: Dave Hansen <dave.hansen@linux.intel.com>
Bounds tables are a significant consumer of memory. It is important
to know when they are being allocated. Add a trace point to trace
whenever an allocation occurs and also its virtual address.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
diff --git a/arch/x86/include/asm/trace/mpx.h b/arch/x86/include/asm/trace/mpx.h
index dcc24f5..9443a5d 100644
--- a/arch/x86/include/asm/trace/mpx.h
+++ b/arch/x86/include/asm/trace/mpx.h
@@ -106,6 +106,22 @@
)
);
+TRACE_EVENT(mpx_new_bounds_table,
+
+ TP_PROTO(unsigned long table_vaddr),
+ TP_ARGS(table_vaddr),
+
+ TP_STRUCT__entry(
+ __field(unsigned long, table_vaddr)
+ ),
+
+ TP_fast_assign(
+ __entry->table_vaddr = table_vaddr;
+ ),
+
+ TP_printk("table vaddr:%p", (void *)__entry->table_vaddr)
+);
+
#endif /* CONFIG_X86_INTEL_MPX */
#undef TRACE_INCLUDE_PATH
diff --git a/arch/x86/mm/mpx.c b/arch/x86/mm/mpx.c
index 3b0b5e6..8f9c6cc 100644
--- a/arch/x86/mm/mpx.c
+++ b/arch/x86/mm/mpx.c
@@ -525,6 +525,7 @@
ret = -EINVAL;
goto out_unmap;
}
+ trace_mpx_new_bounds_table(bt_addr);
return 0;
out_unmap:
vm_munmap(bt_addr, mpx_bt_size_bytes(mm));
