From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: mingo@redhat.com, peterz@infradead.org, irogers@google.com,
namhyung@kernel.org, jolsa@kernel.org, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
ak@linux.intel.com, eranian@google.com, ahmad.yasin@intel.com
Subject: Re: [PATCH V3 0/8] New metricgroup output in perf stat default mode
Date: Thu, 15 Jun 2023 22:41:36 -0400 [thread overview]
Message-ID: <49d5b8f0-7c48-495b-beda-33cbff8e5ef0@linux.intel.com> (raw)
In-Reply-To: <ZIu61WSa17DvVtgt@kernel.org>
On 2023-06-15 9:28 p.m., Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 15, 2023 at 06:53:07AM -0700, kan.liang@linux.intel.com escreveu:
>> The patch proposes a new output format which only outputting the value
>> of each metric and the metricgroup name. It can brings a clean and
>> consistent output format among ARCHs and generations.
>>
>> The first patche is a bug fix for the current code.
>>
>> The patches 2-5 introduce the new metricgroup output.
>>
>> The patches 6-8 improve the tests to cover the default mode.
>
> I cherry picked 1-3 and 6, and pushed to the tmp.perf-tools-next branch
> at both my usual repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tmp.perf-tools-next
>
> And also at the one we're transitioning to, and that Namhyung Kim has
> write access and will update while I'm in vacation in the next two
> weeks.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
>
> Tomorrow I'll do more tests with it and then transition to
> perf-tools-next in both git repositories.
>
> Please prefer
> git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
> from now on.
>
Thanks Arnaldo!
Kan
prev parent reply other threads:[~2023-06-16 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 13:53 [PATCH V3 0/8] New metricgroup output in perf stat default mode kan.liang
2023-06-15 13:53 ` [PATCH V3 1/8] perf evsel: Fix the annotation for hardware events on hybrid kan.liang
2023-06-15 13:53 ` [PATCH V3 2/8] perf metric: JSON flag to default metric group kan.liang
2023-06-15 13:53 ` [PATCH V3 3/8] perf stat,jevents: Introduce Default tags for the default mode kan.liang
2023-06-15 13:53 ` [PATCH V3 4/8] perf metrics: Sort the Default metricgroup kan.liang
2023-06-15 22:05 ` Ian Rogers
2023-06-16 2:15 ` Liang, Kan
2023-06-15 13:53 ` [PATCH V3 5/8] perf stat: New metricgroup output for the default mode kan.liang
2023-06-15 13:53 ` [PATCH V3 6/8] pert tests: Update metric-value for perf stat JSON output kan.liang
2023-06-15 13:53 ` [PATCH V3 7/8] perf test: Move all the check functions of stat csv output to lib kan.liang
2023-06-15 13:53 ` [PATCH V3 8/8] perf test: Add test case for the standard perf stat output kan.liang
2023-06-16 1:28 ` [PATCH V3 0/8] New metricgroup output in perf stat default mode Arnaldo Carvalho de Melo
2023-06-16 2:41 ` Liang, Kan [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=49d5b8f0-7c48-495b-beda-33cbff8e5ef0@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ahmad.yasin@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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.