public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] perf latency command
Date: Sun, 1 Nov 2009 15:55:00 -0600	[thread overview]
Message-ID: <20091101155500.7dd22f19@torg> (raw)

[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]

Ingo,

What follows is a set of three patches against tip/master that
implement a 'latency' sub-command for perf. You can also get it
by fetching the perf-latency-master branch from:

git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-linux.git

The 'perf latency' command is an interface for managing the 
hwlat_detector kernel module via its debufs interface. The kernel 
module polls the TSC looking for gaps and when a gap exceeding a
specified threshold is detected, a timestamp and the gap value (in
microseconds) is printed to stdout.

The command line arguments are a sample interval (--window), sample
duration within that window (--width), a duration for the length of
time the test should run (--duration) and a threshold (--threshold)
above which is considered a hardware latency. 

Clark Williams (3):
  debugfs utility routines for perf
  modify perf routines to use new debugfs routines
  perf latency builtin command

 tools/perf/Documentation/perf-latency.txt |   64 +++++
 tools/perf/Documentation/perf.txt         |    2 +-
 tools/perf/Makefile                       |    3 +
 tools/perf/builtin-latency.c              |  383
 +++++++++++++++++++++++++++++
 tools/perf/builtin.h                      |    2 +-
 tools/perf/command-list.txt               |    1 +
 tools/perf/perf.c                         |   45 +---
 tools/perf/util/debugfs.c                 |  241 ++++++++++++++++++
 tools/perf/util/debugfs.h                 |   22 ++
 tools/perf/util/parse-events.c            |   17 +- 10 files changed,
 727 insertions(+), 53 deletions(-) create mode 100644
 tools/perf/Documentation/perf-latency.txt create mode 100644
 tools/perf/builtin-latency.c create mode 100644
 tools/perf/util/debugfs.c create mode 100644 tools/perf/util/debugfs.h


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-11-01 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 21:55 Clark Williams [this message]
2009-11-01 21:56 ` [PATCH 1/3] debugfs utility routines for perf Clark Williams
2009-11-08 17:06   ` [tip:perf/core] perf tools: Add " tip-bot for Clark Williams
2009-11-01 21:57 ` [PATCH 2/3] modify perf routines to use new debugfs routines Clark Williams
2009-11-08 17:06   ` [tip:perf/core] perf tools: Modify " tip-bot for Clark Williams
2009-11-01 21:58 ` [PATCH 3/3] perf latency builtin command Clark Williams
2009-11-03 19:28   ` Ingo Molnar
2009-11-03 22:00     ` Clark Williams
2009-11-04 12:41       ` 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=20091101155500.7dd22f19@torg \
    --to=williams@redhat.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox