From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
"Taylor, Perry" <perry.taylor@intel.com>,
"Alt, Samantha" <samantha.alt@intel.com>,
"Biggers, Caleb" <caleb.biggers@intel.com>,
"Wang, Weilin" <weilin.wang@intel.com>,
Edward <edward.baker@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Florian Fischer <florian.fischer@muhq.space>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
"Yasin, Ahmad" <ahmad.yasin@intel.com>
Subject: Re: [PATCH v2] perf stat: Introduce skippable evsels
Date: Fri, 21 Apr 2023 13:10:54 -0400 [thread overview]
Message-ID: <c48515e6-6ba1-2c8e-7f84-869e227c5089@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fVnuQ08zUg8XxFhT-oddRd9PC8GPu6q-FU-_H0QLqO91w@mail.gmail.com>
On 2023-04-21 11:49 a.m., Ian Rogers wrote:
>> Can we take a step back? Create a perf/json_metric or whatever branch,
>> fix all the issues thoroughly, and then merge to the mainline.
>>
>> I think the default of perf stat is frequently used by not only the
>> newbees but also the veterans. That could have a big user-visible impact.
>>
>> The 6.4 merge window is approaching. Can we at least revert the patches
>> for 6.4?
>>
>> Arnaldo, what do you think?
> Revert is a complete no go, we'd be reintroducing the bugs that are
> fixed and who will then fix those? How will they be fixed in any way
> other than how they've already been fixed? I've yet to see a
> description of a bug that isn't either:
> 1) an issue because the output formatting changed - the fix here is to
> use CSV or json output, using the hard coded metrics was a bug here
> anyway, not least as the metrics are wrong,
> 2) a pre-existing issue, such as hybrid is broken,
> 3) a non-issue, such as multiplexing on Skylake.
> That's not to say everything couldn't run better, which was the issue
> this patch was looking to address.
Sigh, we really need a clear design and definition regarding the default
of perf stat, especially what is included, what's the expected layout,
the forbidden. So everyone from the developers to the users is on the
same page. Could you please update the document for the default of perf
stat?
One more thing I want to point out is that the json metric may keep
changing. While the kernel metics (only includes the core part of the
json metric) is quite stable. For the default of perf stat, the kernel
metics should be a better choice.
Clarification: I'm not looking for reverting all the patches of the json
metrics in the perf-tool-next branch. The request is to revert the
patches which impact the default of perf stat. More specifically, the
patch 39 and 41.
https://lore.kernel.org/lkml/20230219092848.639226-40-irogers@google.com/
This is really a long discussion. I think we all express the arguments
clearly. Let's make the final decision and stop here.
Arnaldo? Peter? Ingo?
Could you please share your opinions?
Thanks,
Kan
next prev parent reply other threads:[~2023-04-21 17:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 5:19 [PATCH v2] perf stat: Introduce skippable evsels Ian Rogers
2023-04-14 18:02 ` Liang, Kan
2023-04-14 23:03 ` Ian Rogers
2023-04-17 13:58 ` Liang, Kan
2023-04-17 15:59 ` Ian Rogers
2023-04-17 17:31 ` Liang, Kan
2023-04-17 18:13 ` Ian Rogers
2023-04-18 13:03 ` Liang, Kan
2023-04-18 15:43 ` Ian Rogers
2023-04-18 18:19 ` Liang, Kan
2023-04-18 20:08 ` Ian Rogers
2023-04-18 21:51 ` Liang, Kan
2023-04-19 0:12 ` Ian Rogers
2023-04-19 1:00 ` Ian Rogers
2023-04-19 12:31 ` Liang, Kan
2023-04-19 13:19 ` Ian Rogers
2023-04-19 14:16 ` Liang, Kan
2023-04-19 16:51 ` Ian Rogers
2023-04-19 18:57 ` Liang, Kan
2023-04-20 0:23 ` Ian Rogers
2023-04-20 13:02 ` Liang, Kan
2023-04-21 0:19 ` Ian Rogers
2023-04-21 13:32 ` Liang, Kan
2023-04-21 15:49 ` Ian Rogers
2023-04-21 17:10 ` Liang, Kan [this message]
2023-04-21 17:30 ` Ian Rogers
2023-04-21 15:58 ` Ian Rogers
2023-04-20 11:33 ` Arnaldo Carvalho de Melo
2023-04-20 12:22 ` Liang, Kan
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=c48515e6-6ba1-2c8e-7f84-869e227c5089@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=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=edward.baker@intel.com \
--cc=eranian@google.com \
--cc=florian.fischer@muhq.space \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--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=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@intel.com \
/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).