[GIT PULL] xen: replace adhoc debug goo with proper tracing

From: Jeremy Fitzhardinge
Date: Sat Jul 23 2011 - 20:20:24 EST


Hi Linus,

This replaces a pile of ad-hoc debug stuff in the Xen code with tracing, and a few performance improvements noticed as a result.

Thanks,
J

The following changes since commit fe0d42203cb5616eeff68b14576a0f7e2dd56625:

Linux 3.0-rc6 (2011-07-04 15:56:24 -0700)

are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/xen-tracing2

Jeremy Fitzhardinge (17):
trace/xen: add skeleton for Xen trace events
xen/multicalls: remove debugfs stats
xen/trace: set up tracepoint skeleton
xen/trace: add multicall tracing
xen/trace: add mmu tracepoints
xen/trace: add ptpage alloc/release tracepoints
xen/trace: add xen_pgd_(un)pin tracepoints
xen/trace: add segment desc tracing
xen/trace: add tlb flush tracepoints
xen/mmu: use extend_args for more mmuext updates
xen/mmu: tune pgtable alloc/release
xen/multicalls: disable MC_DEBUG
xen/multicalls: add unlikely around slowpath in __xen_mc_entry()
xen/multicall: special-case singleton hypercalls
xen/multicall: move *idx fields to start of mc_buffer
xen/trace: convert mmu events to use DECLARE_EVENT_CLASS()/DEFINE_EVENT()
xen/trace: use class for multicall trace

arch/x86/include/asm/xen/hypercall.h | 22 ++
arch/x86/include/asm/xen/trace_types.h | 18 ++
arch/x86/xen/Makefile | 2 +-
arch/x86/xen/enlighten.c | 16 +-
arch/x86/xen/mmu.c | 139 +++++++--
arch/x86/xen/multicalls.c | 169 +++--------
arch/x86/xen/multicalls.h | 6 +
arch/x86/xen/trace.c | 61 ++++
include/trace/events/xen.h | 504 ++++++++++++++++++++++++++++++++
9 files changed, 787 insertions(+), 150 deletions(-)
create mode 100644 arch/x86/include/asm/xen/trace_types.h
create mode 100644 arch/x86/xen/trace.c
create mode 100644 include/trace/events/xen.h


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/