All of lore.kernel.org
 help / color / mirror / Atom feed
From: jpihet@mvista.com (Jean Pihet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: oprofile: use perf-events framework as backend
Date: Fri, 26 Feb 2010 11:25:04 +0100	[thread overview]
Message-ID: <201002261125.04448.jpihet@mvista.com> (raw)
In-Reply-To: <000501cab6ca$a1ca7710$e55f6530$@deacon@arm.com>

HI Will,

On Friday 26 February 2010 11:01:14 Will Deacon wrote:
> Hi Jean,
>
> Thanks for the feedback.
>
> > How is the underlaying HW reserved? In Oprofile we used to have a call to
> > reserve_pmu.
>
> Since this patch uses the perf API, perf will take care of reserving the
> hardware for us [well, it reserves it for the perf framework]. The events
> created by OProfile are pinned to each CPU, so provided the perf calls
> don't fail, we know that we have access to the PMU. If the calls do fail,
> we report failure back to the generic OProfile framework.
Ok that looks good!

>
> > Otherwise I am OK with the concept of cleaning the profiling tools. Very
> > good!
>
> Thanks. Not only does it clean the code - it adds A9MP support to OProfile
> for free!
Sure, very nice! I was wondering how to maintain both Oprofile and Perf 
Events. You come with the good solution.
I am OK to co-maintain this code if you do not mind.

Thanks,
Jean

>
> Cheers,
>
> Will
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2010-02-26 10:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 18:56 [PATCH 0/6] ARM: oprofile: use perf-events framework as backend Will Deacon
2010-02-25 18:56 ` [PATCH 1/6] ARM: perf-events: add Realview PMU IRQs to pmu.c Will Deacon
2010-02-25 18:56   ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Will Deacon
2010-02-25 18:56     ` [PATCH 3/6] ARM: perf-events: add support for xscale PMUs Will Deacon
2010-02-25 18:56       ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Will Deacon
2010-02-25 18:56         ` [PATCH 5/6] ARM: oprofile: use perf-events framework as backend Will Deacon
2010-02-25 18:56           ` [PATCH 6/6] ARM: oprofile: remove old files and update KConfig Will Deacon
2010-02-26  9:28           ` [PATCH 5/6] ARM: oprofile: use perf-events framework as backend Jean Pihet
2010-02-26 10:01             ` Will Deacon
2010-02-26 10:25               ` Jean Pihet [this message]
2010-03-02 15:54                 ` Will Deacon
2010-02-26  8:23         ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Ingo Molnar
2010-02-26  9:53           ` Will Deacon
2010-02-26  9:10     ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Jean Pihet
2010-02-26 11:17       ` Will Deacon
2010-02-26  9:07 ` [PATCH 0/6] ARM: oprofile: use perf-events framework as backend Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2010-03-10 10:41 [PATCH 0/6] ARM: oprofile: use perf-events framework as backend [v2] Will Deacon
2010-03-10 10:41 ` [PATCH 1/6] ARM: perf-events: add Realview PMU IRQs to pmu.c Will Deacon
2010-03-10 10:41   ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Will Deacon
2010-03-10 10:41     ` [PATCH 3/6] ARM: perf-events: add support for xscale PMUs Will Deacon
2010-03-10 10:41       ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Will Deacon
2010-03-10 10:41         ` [PATCH 5/6] ARM: oprofile: use perf-events framework as backend Will Deacon

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=201002261125.04448.jpihet@mvista.com \
    --to=jpihet@mvista.com \
    --cc=linux-arm-kernel@lists.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 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.