Messages in this thread Patch in this message | | | Subject | [PATCH 06/17] x86, mpx: trace allocation of new bounds tables | From | Dave Hansen <> | Date | Wed, 22 Apr 2015 11:27:37 -0700 |
| |
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> ---
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-04-22 11:16:19.860894373 -0700 +++ b/arch/x86/include/asm/trace/mpx.h 2015-04-22 11:16:19.865894598 -0700 @@ -85,6 +85,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-04-22 11:16:19.862894463 -0700 +++ b/arch/x86/mm/mpx.c 2015-04-22 11:16:19.866894643 -0700 @@ -485,6 +485,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); _
| |