From: William Cohen <wcohen@nc.rr.com>
To: eranian@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, perfmon@napali.hpl.hp.com,
perfctr-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: Re: [Perfctr-devel] 2.6.16-rc5 perfmon2 new code base + libpfm with Montecito support
Date: Mon, 13 Mar 2006 14:15:53 -0500 [thread overview]
Message-ID: <4415C4E9.5070702@nc.rr.com> (raw)
In-Reply-To: <20060313185500.GB32683@frankl.hpl.hp.com>
Stephane Eranian wrote:
> Will,
>
> On Mon, Mar 13, 2006 at 01:39:01PM -0500, William Cohen wrote:
>
>>Hi Stephane,
>>
>>I have been looking through the perfmon2 code to see how it is going to
>>work with OProfile. It looks like the ia64 oprofile support has not been
>>modified to work with the changes in perfmon2. Has the ia64 kernel been
>>built with perfmon2 and oprofile support? I don't have easy access to an
>>ia64, so I haven't been able to verify that the attached patch works.
>>However, I expect that the changes in the patch will be required for
>>OProfile to function with perfmon2.
>>
>
> Good timing. I just fixed this today. Now it compiles fine on
> IA64. I also started looking into using the same technique on
> i386. It is very easy. It looks like opcontrol or ophelp
> would need to be updated. I think the trick is to make
> sure that ophelp knows the PMU mapping used by perfmon2,
> i.e., knows that PERFEVTSEL0 is PMC0 for instance.
>
Yes, I have a similar patch for i386 in the kernel. I don't yet have
modifications for opcontrol or ophelp.
One question would be identifying the processor when using the perfmon2
support for i386/* processors? There is prior support in the oprofile
driver for i386 processors. Identify the processor differently depending
on whether perfmon2 is being used to distinguish between the different
interfaces? The way that OProfile has the events each name processor
requires a different directory in /usr/share/oprofile. Would prefer to
keep down the proliferation of new directories.
-Will
next prev parent reply other threads:[~2006-03-13 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 15:53 2.6.16-rc5 perfmon2 new code base + libpfm with Montecito support Stephane Eranian
2006-03-08 20:40 ` William Cohen
2006-03-08 21:22 ` Stephane Eranian
2006-03-13 18:39 ` [Perfctr-devel] " William Cohen
2006-03-13 18:55 ` Stephane Eranian
2006-03-13 19:15 ` William Cohen [this message]
2006-03-13 20:25 ` Stephane Eranian
2006-03-13 20:58 ` William Cohen
2006-03-13 21:21 ` Stephane Eranian
[not found] ` <20060313210127.GA13453@totally.trollied.org>
[not found] ` <20060313210354.GG32683@frankl.hpl.hp.com>
[not found] ` <20060313232057.GA16582@totally.trollied.org>
2006-03-13 23:58 ` 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=4415C4E9.5070702@nc.rr.com \
--to=wcohen@nc.rr.com \
--cc=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.com \
/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