public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	Mikael Pettersson <mikpe@it.uu.se>,
	Robert Richter <robert.richter@amd.com>,
	oprofile-list@lists.sf.net, Ingo Molnar <mingo@elte.hu>,
	Jiri Kosina <jkosina@suse.cz>, Jiri Benc <jbenc@suse.cz>,
	Vilem Marsik <vmarsik@suse.cz>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org, eranian@googlemail.com
Subject: Re: Oprofile : need to adjust PC by 16 bytes
Date: Sat, 15 Nov 2008 19:36:27 +0100	[thread overview]
Message-ID: <20081115183627.GL3810@one.firstfloor.org> (raw)
In-Reply-To: <491EF942.1090709@cosmosbay.com>

On Sat, Nov 15, 2008 at 05:30:58PM +0100, Eric Dumazet wrote:
> Andi Kleen a écrit :
> >>>And no, blindly subtracting 16 from IP is not a fix.
> >>Who mentioned a fix ? I am only giving more fuel to Intel guys so they
> >>hopefully can give us a working oprofile.
> >
> >You would need to implement PEBS support to avoid that problem. But it's a 
> >big
> >task. perfmon2 implements it already.
> >
> 
> Thanks for the information.
> 
> Hum, so I grabbed perfmon2 git tree, installed various tools...
> 
> I am quite new to pfmon and tried :
> 
> # pfmon --system-wide
> sizeof=64 44
> <press ENTER to stop session>
> 
> Then started "tbench 8", and got a kernel panic after 6 seconds.
> 
> 
> I was using oprofile like this
> 
> opcontrol --vmlinux=/path/vmlinux --start
> // doing some benchmarking...
> opreport -l vmlinux | head -n 40
> 
> 
> What would be a working equivalent for perfmon2 based tools ?

Probably getting a perfmon tree that works. I guess Stephane
can help (cc'ed).  Or just deal with imprecise events for now.

-Andi
-- 
ak@linux.intel.com

  reply	other threads:[~2008-11-15 18:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 20:57 Oprofile [still] doesn't work on 2.6.28-rc4 on certain CPU Jiri Kosina
2008-11-13 21:24 ` Ingo Molnar
2008-11-13 21:27   ` Jiri Kosina
2008-11-13 21:37     ` Ingo Molnar
2008-11-13 21:49       ` Eric Dumazet
2008-11-14 15:25         ` Oprofile : need to adjust PC by 16 bytes Eric Dumazet
2008-11-14 15:59           ` Andi Kleen
2008-11-14 16:02             ` Eric Dumazet
2008-11-14 17:01           ` Mikael Pettersson
2008-11-14 17:21             ` Eric Dumazet
2008-11-14 17:50               ` Andi Kleen
2008-11-15 16:30                 ` Eric Dumazet
2008-11-15 18:36                   ` Andi Kleen [this message]
2008-11-17 15:02                     ` stephane eranian
2008-11-17 15:16                       ` Eric Dumazet
2008-11-17 15:24                       ` Andi Kleen
2008-11-14 10:09     ` Oprofile [still] doesn't work on 2.6.28-rc4 on certain CPU Robert Richter
2008-11-14 11:12       ` Jiri Kosina
2008-11-13 21:33   ` Maynard Johnson

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=20081115183627.GL3810@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=dada1@cosmosbay.com \
    --cc=eranian@googlemail.com \
    --cc=jbenc@suse.cz \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mingo@elte.hu \
    --cc=oprofile-list@lists.sf.net \
    --cc=penberg@cs.helsinki.fi \
    --cc=robert.richter@amd.com \
    --cc=vmarsik@suse.cz \
    /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