All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, tglx@linutronix.de,
	markus.t.metzger@gmail.com, roland@redhat.com,
	akpm@linux-foundation.org, mtk.manpages@gmail.com,
	eranian@googlemail.com, juan.villacis@intel.com
Subject: Re: [patch 9/9] x86, bts, ftrace: a BTS ftrace plug-in prototype
Date: Tue, 25 Nov 2008 17:33:50 +0100	[thread overview]
Message-ID: <20081125163350.GC22504@elte.hu> (raw)
In-Reply-To: <20081125092415.A31432@sedona.ch.intel.com>


* Markus Metzger <markus.t.metzger@intel.com> wrote:

> A prototype for a BTS ftrace plug-in.
> 
> The tracer collects branch trace in a cyclic buffer for each cpu.
> 
> The tracer is not configurable and the trace for each snapshot is 
> appended when doing cat /debug/tracing/trace.
> 
> This is a proof of concept that will be extended with future patches 
> to become a (hopefully) useful tool.
> 
> Signed-off-by: Markus Metzger <markus.t.metzger@intel.com>

very nice stuff!

i've created a new topic branch for this: 

   tip/tracing/hw-branch-tracing

and applied your patches there. (applied the earlier x86 patches in 
their appropriate x86 topic branches)

Integrated the end result into tip/master and have started testing it.

I've got a few more review comments as well - will post them as a 
reply to the respective patches.

	Ingo

  parent reply	other threads:[~2008-11-25 16:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  8:24 [patch 9/9] x86, bts, ftrace: a BTS ftrace plug-in prototype Markus Metzger
2008-11-25 10:12 ` Andi Kleen
2008-11-25 10:25   ` Metzger, Markus T
2008-11-25 10:39 ` Frédéric Weisbecker
2008-11-25 11:23   ` Metzger, Markus T
2008-11-25 11:30     ` Frédéric Weisbecker
2008-11-25 16:33 ` Ingo Molnar [this message]
2008-11-25 16:40 ` Ingo Molnar

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=20081125163350.GC22504@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=eranian@googlemail.com \
    --cc=hpa@zytor.com \
    --cc=juan.villacis@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@gmail.com \
    --cc=markus.t.metzger@intel.com \
    --cc=mtk.manpages@gmail.com \
    --cc=roland@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.