[PATCH 00/15] xen: use tracing to replace ad-hoc debug/stats stuff

From: Jeremy Fitzhardinge
Date: Mon Jun 20 2011 - 18:16:38 EST


From: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>

Hi all,

This series (RFC for 3.1) introduces a set of trace events to keep
track of what's going on within the Xen code. This allows us to
replace a pile of ad-hoc debug and stats code.

The latter part of the series implements some improvements the better
tracing highlighted, specifically to reduce hypercall overhead by
making multicalls cheaper and to increase the multicall batch size.

Also at git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/xen-tracing2

Thanks,
J

Jeremy Fitzhardinge (15):
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

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 | 534 ++++++++++++++++++++++++++++++++
9 files changed, 817 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

--
1.7.5.4

--
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/