linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Andi Kleen <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/6] perf dlfilter: Add dlfilter-show-cycles
Date: Tue, 26 Oct 2021 12:01:46 +0300	[thread overview]
Message-ID: <20211026090152.357591-1-adrian.hunter@intel.com> (raw)

Hi

The issue with V1 was that the IPC information used to accumulate cycle
counts has a lower granularity because it is output only when the cycle
count correlates to the IP of the event i.e. only when the IPC is exactly
correct.

To enable more frequent updates to the cycle count, itrace option 'A' is
added, which specifies that IPC information can be approximate.

In addition there are some new miscellaneous patches.


Changes in V2:

    perf dlfilter: Add dlfilter-show-cycles
      Separate counts for branches, instructions or other events.

    New patches:
      perf auxtrace: Add missing Z option to ITRACE_HELP
      perf auxtrace: Add itrace A option to approximate IPC
      perf intel-pt: Support itrace A option to approximate IPC
      perf auxtrace: Add itrace d+o option to direct debug log to stdout
      perf intel-pt: Support itrace d+o option to direct debug log to stdout


Adrian Hunter (6):
      perf auxtrace: Add missing Z option to ITRACE_HELP
      perf auxtrace: Add itrace A option to approximate IPC
      perf intel-pt: Support itrace A option to approximate IPC
      perf dlfilter: Add dlfilter-show-cycles
      perf auxtrace: Add itrace d+o option to direct debug log to stdout
      perf intel-pt: Support itrace d+o option to direct debug log to stdout

 tools/perf/Documentation/itrace.txt                |   2 +
 tools/perf/Documentation/perf-intel-pt.txt         |  23 ++++
 tools/perf/Makefile.perf                           |   2 +-
 tools/perf/dlfilters/dlfilter-show-cycles.c        | 144 +++++++++++++++++++++
 tools/perf/util/auxtrace.c                         |   3 +
 tools/perf/util/auxtrace.h                         |   6 +
 .../perf/util/intel-pt-decoder/intel-pt-decoder.c  |   1 +
 .../perf/util/intel-pt-decoder/intel-pt-decoder.h  |   1 +
 tools/perf/util/intel-pt-decoder/intel-pt-log.c    |   8 +-
 tools/perf/util/intel-pt.c                         |  21 ++-
 10 files changed, 200 insertions(+), 11 deletions(-)
 create mode 100644 tools/perf/dlfilters/dlfilter-show-cycles.c


Regards
Adrian

             reply	other threads:[~2021-10-26  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  9:01 Adrian Hunter [this message]
2021-10-26  9:01 ` [PATCH V2 1/6] perf auxtrace: Add missing Z option to ITRACE_HELP Adrian Hunter
2021-10-26  9:01 ` [PATCH V2 2/6] perf auxtrace: Add itrace A option to approximate IPC Adrian Hunter
2021-10-26  9:01 ` [PATCH V2 3/6] perf intel-pt: Support " Adrian Hunter
2021-10-26 17:03   ` Andi Kleen
2021-10-26  9:01 ` [PATCH V2 4/6] perf dlfilter: Add dlfilter-show-cycles Adrian Hunter
2021-10-26  9:01 ` [PATCH V2 5/6] perf auxtrace: Add itrace d+o option to direct debug log to stdout Adrian Hunter
2021-10-26  9:01 ` [PATCH V2 6/6] perf intel-pt: Support " Adrian Hunter
     [not found]   ` <dd9f91af-8b74-bf75-b3a4-c3826be7b190@linux.intel.com>
2021-10-27 18:59     ` Arnaldo Carvalho de Melo

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=20211026090152.357591-1-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).