From: Dave Hansen <dave.han...@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.han...@linux.intel.com>
Reviewed-by: Thomas Gleixner <t...@linutronix.de>
---
b/arch/x86/include/asm/trace/mpx.h | 16 ++++++++++++++++
b/arch/x86/mm/mpx.c | 1 +
2 files changed, 17 insertions(+)
diff -puN arch/x86/include/asm/trace/mpx.h~trace_mpx_new_bounds_table
arch/x86/include/asm/trace/mpx.h
--- a/arch/x86/include/asm/trace/mpx.h~trace_mpx_new_bounds_table
2015-06-01 10:24:07.357872090 -0700
+++ b/arch/x86/include/asm/trace/mpx.h 2015-06-01 10:24:07.362872315 -0700
@@ -95,6 +95,22 @@ DEFINE_EVENT(mpx_range_trace, mpx_unmap_
TP_ARGS(start, end)
);
+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)
+);
+
#else
/*
diff -puN arch/x86/mm/mpx.c~trace_mpx_new_bounds_table arch/x86/mm/mpx.c
--- a/arch/x86/mm/mpx.c~trace_mpx_new_bounds_table 2015-06-01
10:24:07.359872180 -0700
+++ b/arch/x86/mm/mpx.c 2015-06-01 10:24:07.363872360 -0700
@@ -483,6 +483,7 @@ static int allocate_bt(long __user *bd_e
ret = -EINVAL;
goto out_unmap;
}
+ trace_mpx_new_bounds_table(bt_addr);
return 0;
out_unmap:
vm_munmap(bt_addr & MPX_BT_ADDR_MASK, MPX_BT_SIZE_BYTES);
_
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
