All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Like Xu <like.xu.linux@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/perf/design: Synchronize the definition of enum perf_hw_id with code
Date: Thu, 11 Nov 2021 14:50:26 -0300	[thread overview]
Message-ID: <YY1X4gO/yydGu+11@kernel.org> (raw)
In-Reply-To: <20211109090147.56978-1-likexu@tencent.com>

Em Tue, Nov 09, 2021 at 05:01:47PM +0800, Like Xu escreveu:
> From: Like Xu <likexu@tencent.com>
> 
> We're not surprised that there are tons of Linux users who
> only read the documentation to learn about the kernel.
> 
> Let's update the perf part for common hardware events
> since three new *generic* hardware events were added.

Thanks, applied.

- Arnaldo

 
> Signed-off-by: Like Xu <likexu@tencent.com>
> ---
>  tools/perf/design.txt | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/tools/perf/design.txt b/tools/perf/design.txt
> index a42fab308ff6..aa8cfeabb743 100644
> --- a/tools/perf/design.txt
> +++ b/tools/perf/design.txt
> @@ -106,6 +106,9 @@ enum perf_hw_id {
>  	PERF_COUNT_HW_BRANCH_INSTRUCTIONS	= 4,
>  	PERF_COUNT_HW_BRANCH_MISSES		= 5,
>  	PERF_COUNT_HW_BUS_CYCLES		= 6,
> +	PERF_COUNT_HW_STALLED_CYCLES_FRONTEND	= 7,
> +	PERF_COUNT_HW_STALLED_CYCLES_BACKEND	= 8,
> +	PERF_COUNT_HW_REF_CPU_CYCLES		= 9,
>  };
>  
>  These are standardized types of events that work relatively uniformly
> -- 
> 2.33.0

-- 

- Arnaldo

      reply	other threads:[~2021-11-11 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  9:01 [PATCH] tools/perf/design: Synchronize the definition of enum perf_hw_id with code Like Xu
2021-11-11 17:50 ` Arnaldo Carvalho de Melo [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=YY1X4gO/yydGu+11@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=like.xu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@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.