From: Philip Mucci <mucci@cs.utk.edu>
To: eranian@hpl.hp.com
Cc: perfmon@napali.hpl.hp.com, Linux-mips@linux-mips.org,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [perfmon] Re: 2.6.13-rc2 perfmon2 new code base with MIPS5K/20K support + libpfm available
Date: Thu, 19 Jan 2006 20:30:33 +0100 [thread overview]
Message-ID: <1137699033.15290.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20060119191403.GV19622@frankl.hpl.hp.com>
Yup...just looked at the code...should be simple to adapt...I'll give it
a spin on perfmon2...the only thing that seems to be obviously wrong are
the missing arguments to PFM_CREATE_CONTEXT.
Phil
On Thu, 2006-01-19 at 11:14 -0800, Stephane Eranian wrote:
> Phil,
>
> On Thu, Jan 19, 2006 at 07:38:56PM +0100, Philip Mucci wrote:
> > Stefane,
> >
> > Are you saying that oprofile user level tools don't even use the
> > oprofile driver but rather just set up a system-wide IP-sampling context
> > for perfmon2?
> >
> Yes, I think that is the way this works. I will verify this.
>
> > Think of all the work that Ralf just did. ;-)
> >
> If you don't have perfmon2, then you have to provide you arch/mips/oprofile
> files for sure.
> _______________________________________________
> perfmon mailing list
> perfmon@linux.hpl.hp.com
> http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/
next prev parent reply other threads:[~2006-01-19 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 10:30 2.6.13-rc2 perfmon2 new code base with MIPS5K/20K support + libpfm available Philip Mucci
2006-01-19 13:36 ` Ralf Baechle
2006-01-19 14:04 ` Philip Mucci
2006-01-19 15:33 ` Nigel Stephens
2006-01-19 15:41 ` Philip Mucci
2006-01-19 18:16 ` Stephane Eranian
2006-01-19 18:38 ` [perfmon] " Philip Mucci
2006-01-19 19:14 ` Stephane Eranian
2006-01-19 19:30 ` Philip Mucci [this message]
2006-01-19 19:59 ` Stephane Eranian
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=1137699033.15290.36.camel@localhost.localdomain \
--to=mucci@cs.utk.edu \
--cc=Linux-mips@linux-mips.org \
--cc=eranian@hpl.hp.com \
--cc=perfmon@napali.hpl.hp.com \
--cc=ralf@linux-mips.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