[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150207102255.2ed95393@grimm.local.home>
Date: Sat, 7 Feb 2015 10:22:55 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sedat Dilek <sedat.dilek@...il.com>
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>, Dave Hansen <dave@...1.net>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
linux-next <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Kristen Carlson Accardi <kristen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
On Sat, 7 Feb 2015 09:13:23 +0100
Sedat Dilek <sedat.dilek@...il.com> wrote:
I fell over this w/o having any experiences in using the tracing
> system within the Linux-kernel.
> Can you give a brief introduction?
> Or can describe how you made your tests?
> Did you use trace-cmd in your tests?
>
>
Some of the tests use trace-cmd, others use perf, most just do echo and
cat into the tracing directory itself.
I've added these over the years and need to clean them up and put them
someplace public. Right now they are very specific to my machines.
There's also tests in tools/testing/selftests/ftrace. But the rules
for what can go into selftests limit what I can place in there. I will
be adding more tests there soon though.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists