From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Gaurav Singh <gausinghnsit@gmail.com>
Cc: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org
Subject: Re: PMC support for ARMv6
Date: Thu, 15 Jan 2009 15:32:28 -0500 [thread overview]
Message-ID: <20090115203228.GA4284@Krystal> (raw)
In-Reply-To: <3cc7a0df0901132148r1a3c0fa8q4c8d5912655eccc2@mail.gmail.com>
* Gaurav Singh (gausinghnsit@gmail.com) wrote:
> Hi Mathieu / all,
> I have integrated PMC in ARMv6 primarily for 2 aims:
> 1. CPI calculations - this trace_mark is triggered triggered after X no. of
> clock cycles. The number of instructions executed and the no. of clock
> cycles is noted.
> 2. Cache Hit rate calculation - Here I have not used the PMC registers in
> the ARM processor - rather have used L2 Cache controller registers to find
> out this information - but this does not provide information about the L1
> cache hit/miss behaviour.
>
> Any other suggestions on what else can be done in PMC?
>
I'd like to see this trace_mark turned into a tracepoint probe. Having a
periodical interrupt which saves this information is good, but I would
also like to have a tracepoint probe that we could attach at important
execution sites, like sched change, irq, softirq, nmi entry/exit where
we would read the performance counter.
> Also have ported LTTng to 2.6.24 for two Nomadik Boards - NDK15 and
> NDK20. Doing some tests and will send it over to you guys soon for your
> comments.
>
I'd be interested in merging your patchesfor 2.6.28 into the LTTng tree.
Please keep us posted.
Mathieu
> Cheers!
> Have a Nice Day!
> Gaurav
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
parent reply other threads:[~2009-01-15 21:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3cc7a0df0901132148r1a3c0fa8q4c8d5912655eccc2@mail.gmail.com>]
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=20090115203228.GA4284@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=gausinghnsit@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.