From: Borislav Petkov <bp@amd64.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "acme@infradead.org" <acme@infradead.org>,
"fweisbec@gmail.com" <fweisbec@gmail.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>
Subject: Re: [RFC PATCH 5/9] perf: Move trace stuff into tools/lib/trace
Date: Wed, 1 Sep 2010 10:10:13 +0200 [thread overview]
Message-ID: <20100901081013.GA23512@aftab> (raw)
In-Reply-To: <1283300144.1377.864.camel@gandalf.stny.rr.com>
From: Steven Rostedt <rostedt@goodmis.org>
Date: Tue, Aug 31, 2010 at 08:15:44PM -0400
> On Fri, 2010-08-06 at 16:25 +0200, Borislav Petkov wrote:
> > From: Borislav Petkov <borislav.petkov@amd.com>
> >
> > Move tracing stuff into tools/lib/trace and rewire it back into perf.
> > Add a top-level Makefile which selects between targets depending
> > on the tool we want to build.
> >
> > Also, add a Makefile.lib for common facilities used by all the
> > Makefiles. While at it, make sure objects output directory using O=
> > exists.
> >
> > Finally, rename trace/util.h to trace/trace-util.h so as not to
> > conflict
> > with perf's util.h.
> >
> > Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
> > ---
>
>
> I'll merge this patch into my tree, and that should make it easier for
> you.
Yeah, that's cool. FYI, Arnaldo wanted to have that toplevel-Makefile
thing too (tools/Makefile) so there might be some conflicts depending on
how far he is.
Thanks Steven.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-09-01 8:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 14:25 [RFC PATCH 00/9] RAS daemon prototype, v2 Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 1/9] x86, mce: Notify about corrected events too Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 2/9] amd64_edac: Remove polling mechanism Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 3/9] perf_events: Export an assortment of functions Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 4/9] mce: Add persistent events Borislav Petkov
2010-08-06 14:57 ` Peter Zijlstra
2010-09-01 0:13 ` Steven Rostedt
2010-09-01 6:14 ` Ingo Molnar
2010-09-01 14:54 ` Steven Rostedt
2010-08-06 14:25 ` [RFC PATCH 5/9] perf: Move trace stuff into tools/lib/trace Borislav Petkov
2010-09-01 0:15 ` Steven Rostedt
2010-09-01 8:10 ` Borislav Petkov [this message]
2010-09-01 14:55 ` Steven Rostedt
2010-08-06 14:25 ` [RFC PATCH 6/9] perf: Export debugfs utilities Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 7/9] perf: Export cpumap Borislav Petkov
2010-08-06 14:39 ` Arnaldo Carvalho de Melo
2010-08-06 14:49 ` Borislav Petkov
2010-08-06 15:14 ` Arnaldo Carvalho de Melo
2010-08-06 16:04 ` Borislav Petkov
2010-08-06 21:48 ` Arnaldo Carvalho de Melo
2010-08-06 14:25 ` [RFC PATCH 8/9] perf: Carve out mmap helpers for general use Borislav Petkov
2010-08-06 14:25 ` [RFC PATCH 9/9] tools, ras: Add a RAS daemon Borislav Petkov
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=20100901081013.GA23512@aftab \
--to=bp@amd64.org \
--cc=Borislav.Petkov@amd.com \
--cc=acme@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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.