From: Robert Richter <robert.richter@amd.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/6] ARM: Make oprofile depend on CONFIG_HW_PERF_EVENTS
Date: Thu, 16 Sep 2010 13:34:44 +0000 [thread overview]
Message-ID: <20100916133444.GB13563@erda.amd.com> (raw)
In-Reply-To: <831bc9523fe04ce899bc78230990033fbe009431.1284357372.git.matt@console-pimps.org>
On 13.09.10 04:39:52, Will Deacon wrote:
> Hi Matt,
>
> On Mon, 2010-09-13 at 07:07 +0100, Matt Fleming wrote:
> > Currently, oprofile support is only functional if CONFIG_HW_PERF_EVENTS
> > is set. If this symbol is not set, oprofile initialisation will fail at
> > runtime. Instead of allowing the oprofile code to build but fail at
> > runtime it seems less confusing to not allow the code to be built unless
> > hardware performance counter support is available.
> >
> > Signed-off-by: Matt Fleming <matt@console-pimps.org>
> > ---
> > arch/arm/Kconfig | 2 +-
> > arch/arm/oprofile/common.c | 9 ---------
> > 2 files changed, 1 insertions(+), 10 deletions(-)
> When oprofile_arch_init fails (-ENODEV), oprofile will fall back to
> timer mode. With this patch, how can you make use of a timer fallback?
True, if you want an error at compile time, maybe we use the #error
pragma instead. But falling back to timer mode is fine to me too.
Will leave that decision to the arm folks.
-Robert
>
> I'll try and get around to testing the rest of this series today.
>
> Cheers,
>
> Will
>
>
>
>
--
Advanced Micro Devices, Inc.
Operating System Research Center
prev parent reply other threads:[~2010-09-16 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 6:07 [PATCH 5/6] ARM: Make oprofile depend on CONFIG_HW_PERF_EVENTS Matt Fleming
2010-09-13 8:39 ` Will Deacon
2010-09-13 9:22 ` Sergei Shtylyov
2010-09-16 13:34 ` Robert Richter [this message]
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=20100916133444.GB13563@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-sh@vger.kernel.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