mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] perf script: Add script to collect and display IBS samples
Date: Fri, 9 Mar 2012 12:41:12 +0100	[thread overview]
Message-ID: <20120309114112.GR16322@erda.amd.com> (raw)
In-Reply-To: <20120308121924.GA19674@elte.hu>

Ingo,

On 08.03.12 13:19:24, Ingo Molnar wrote:
> I've applied the following 4 kernel patches to perf/x86-ibs:
> 
>  db98c5faf8cb: perf/x86: Implement 64-bit counter support for IBS
>  4db2e8e6500d: perf/x86: Implement IBS pmu control ops
>  b7074f1fbd61: perf/x86: Implement IBS interrupt handler
>  510419435c69: perf/x86: Implement IBS event configuration
> 
> and pushed it out.
> 
> We can apply any tooling changes to this branch as well.
> 
> I suspect being able to skid-less profile on AMD CPUs, using 
> IBS, would be a useful feature to users. What would be required 
> for that to work?

thanks for putting this into tip. This helps a lot.

I am just looking into skid-less sampling. The effort of attaching the
rip taken from the IBS sample for events 0x76/0xc1 should be feasable.

In between I started the implementation of ibs pseudo events as
described here:

 Appendix F Guide to Instruction-Based Sampling
 http://support.amd.com/us/Processor_TechDocs/47414_15h_sw_opt_guide.pdf

This includes kernel side filtering and ibs support for the perf tool.

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center


  reply	other threads:[~2012-03-09 11:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 17:23 [PATCH 0/4] perf tools: Add support for IBS Robert Richter
2011-12-15 17:23 ` [PATCH 1/4] perf tool: Parse general/raw events from sysfs Robert Richter
2011-12-21 16:52   ` Robert Richter
2012-01-02 11:07   ` Stephane Eranian
2011-12-15 17:23 ` [PATCH 2/4] perf tools: Add pmu mappings to header information Robert Richter
2011-12-15 17:23 ` [PATCH 3/4] perf script: Add generic perl handler to process events Robert Richter
2011-12-29 20:56   ` [tip:perf/core] " tip-bot for Robert Richter
2011-12-15 17:23 ` [PATCH 4/4] perf script: Add script to collect and display IBS samples Robert Richter
2011-12-15 19:19   ` David Ahern
2011-12-15 23:47     ` Robert Richter
2011-12-23 10:33   ` Ingo Molnar
2011-12-23 11:19     ` Robert Richter
2011-12-23 13:53       ` Ingo Molnar
2011-12-23 14:14         ` Peter Zijlstra
2011-12-23 14:40           ` Ingo Molnar
2011-12-23 16:17             ` Robert Richter
2011-12-23 16:39               ` Ingo Molnar
2011-12-23 16:50                 ` Robert Richter
2011-12-30  9:55                   ` Ingo Molnar
2012-02-02 11:21                     ` Robert Richter
2012-03-08 12:19                       ` Ingo Molnar
2012-03-09 11:41                         ` Robert Richter [this message]
2012-03-21 18:13                           ` Robert Richter
2012-03-22  7:51                             ` 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=20120309114112.GR16322@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=acme@redhat.com \
    --cc=eranian@google.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

Powered by JetHome