From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kan.liang@linux.intel.com
Cc: irogers@google.com, namhyung@kernel.org, mark.rutland@arm.com,
maz@kernel.org, marcan@marcan.st, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V4 2/2] perf top: Uniform the event name for the hybrid machine
Date: Thu, 14 Dec 2023 19:14:40 -0300 [thread overview]
Message-ID: <ZXt-UC-gkFPQofza@kernel.org> (raw)
In-Reply-To: <20231214144612.1092028-2-kan.liang@linux.intel.com>
Em Thu, Dec 14, 2023 at 06:46:12AM -0800, kan.liang@linux.intel.com escreveu:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> It's hard to distinguish the default cycles events among hybrid PMUs.
> For example,
>
> $perf top
> Available samples
> 385 cycles:P
> 903 cycles:P
Thanks, tested and applied both patches to perf-tools-next.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
prev parent reply other threads:[~2023-12-14 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 14:46 [PATCH V4 1/2] perf top: Use evsel's cpus to replace user_requested_cpus kan.liang
2023-12-14 14:46 ` [PATCH V4 2/2] perf top: Uniform the event name for the hybrid machine kan.liang
2023-12-14 22:14 ` 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=ZXt-UC-gkFPQofza@kernel.org \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).