public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [GIT PULL] xen: replace adhoc debug goo with proper tracing
Date: Fri, 22 Jul 2011 15:17:34 -0700	[thread overview]
Message-ID: <4E29F6FE.6030004@goop.org> (raw)

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



                 reply	other threads:[~2011-07-24  0:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E29F6FE.6030004@goop.org \
    --to=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox