public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf_counters: start documenting HAVE_PERF_COUNTERS requirements
Date: Fri, 12 Jun 2009 10:17:50 -0700	[thread overview]
Message-ID: <4A328DBE.2030905@oracle.com> (raw)
In-Reply-To: <1244827063-24046-1-git-send-email-vapier@gentoo.org>

Mike Frysinger wrote:
> Help out arch porters who want to support perf counters by listing some
> basic requirements.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> i imagine more details would be good, but this is a starting point and
> better than nothing
> 
>  init/Kconfig          |    2 ++
>  tools/perf/design.txt |   15 +++++++++++++++
>  2 files changed, 17 insertions(+), 0 deletions(-)
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index c649657..20f85b1 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -936,6 +936,8 @@ config AIO
>  
>  config HAVE_PERF_COUNTERS
>  	bool
> +	help
> +	  See end of tools/perf/design.txt

How about
	  See "Arch requirements" in tools/perf/design.txt
since it doesn't need to be at the end of the file forever.

>  
>  menu "Performance Counters"
>  
> diff --git a/tools/perf/design.txt b/tools/perf/design.txt
> index 860e116..f71e0d2 100644
> --- a/tools/perf/design.txt
> +++ b/tools/perf/design.txt
> @@ -440,3 +440,18 @@ by this process or by another, and doesn't affect any counters that
>  this process has created on other processes.  It only enables or
>  disables the group leaders, not any other members in the groups.
>  
> +
> +Arch requirements
> +-----------------
> +
> +If your architecture does not have hardware performance metrics, you can
> +still use the generic software counters based on hrtimers for sampling.
> +
> +So to start with, in order to add HAVE_PERF_COUNTERS to your Kconfig, you
> +will need at least this:
> +	- asm/perf_counter.h - a basic stub will suffice at first
> +	- support for atomic64 types (and associated helper functions)
> +	- set_perf_counter_pending() implemented
> +
> +If your architecture does have hardware capabilities, you can override the
> +weak stub hw_perf_counter_init() to register hardware counters.


-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

  reply	other threads:[~2009-06-12 17:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 17:17 [PATCH] perf_counters: start documenting HAVE_PERF_COUNTERS requirements Mike Frysinger
2009-06-12 17:17 ` Randy Dunlap [this message]
2009-06-12 17:27   ` Mike Frysinger
2009-06-14  9:41     ` Paul Mundt
2009-06-14  9:51       ` Mike Frysinger
2009-06-12 17:30 ` Ingo Molnar
2009-06-12 17:32   ` Mike Frysinger
2009-06-12 17:36     ` Ingo Molnar
2009-06-12 17:40       ` Mike Frysinger
2009-06-12 17:40         ` Randy Dunlap
2009-06-12 17:56           ` Sam Ravnborg
2009-06-12 17:53             ` Randy Dunlap
2009-06-12 17:33 ` [tip:perfcounters/core] perf_counter: Start " tip-bot for Mike Frysinger
2009-06-12 17:39 ` tip-bot for Mike Frysinger

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=4A328DBE.2030905@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=vapier@gentoo.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