From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Yongwei Ma <yongwei.ma@intel.com>,
Dapeng Mi <dapeng1.mi@intel.com>
Subject: Re: [Patch v3 0/5] Bug fixes on topdown events reordering
Date: Mon, 12 Aug 2024 13:43:39 +0800 [thread overview]
Message-ID: <5de31aa1-8103-4f73-8134-4efe04a73295@linux.intel.com> (raw)
In-Reply-To: <20240712170339.185824-1-dapeng1.mi@linux.intel.com>
Hi Ian,
Kindly ping, any comments here? Thanks.
On 7/13/2024 1:03 AM, Dapeng Mi wrote:
> Changes:
> v2 -> v3:
> * Refine arch_is_topdown_metrics() (Kan Liang)
> * Only move topdown metric events forward when they are not in the
> group with previous event (Ian)
> * Check if topdown events is supported before test topown events
> leader sampling (Kan Liang)
>
> History:
> v1: https://lore.kernel.org/all/20240702224037.343958-1-dapeng1.mi@linux.intel.com/
> v2: https://lore.kernel.org/all/20240708144204.839486-1-dapeng1.mi@linux.intel.com/
>
>
> Dapeng Mi (5):
> perf x86/topdown: Complete topdown slots/metrics events check
> perf x86/topdown: Correct leader selection with sample_read enabled
> perf x86/topdown: Don't move topdown metric events in group
> perf tests: Add leader sampling test in record tests
> perf tests: Add topdown events counting and sampling tests
>
> tools/perf/arch/x86/util/evlist.c | 13 +++++--
> tools/perf/arch/x86/util/evsel.c | 3 +-
> tools/perf/arch/x86/util/topdown.c | 62 +++++++++++++++++++++++++++++-
> tools/perf/arch/x86/util/topdown.h | 2 +
> tools/perf/tests/shell/record.sh | 45 ++++++++++++++++++++++
> tools/perf/tests/shell/stat.sh | 6 +++
> 6 files changed, 124 insertions(+), 7 deletions(-)
>
>
> base-commit: 73e931504f8e0d42978bfcda37b323dbbd1afc08
prev parent reply other threads:[~2024-08-12 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 17:03 [Patch v3 0/5] Bug fixes on topdown events reordering Dapeng Mi
2024-07-12 17:03 ` [Patch v3 1/5] perf x86/topdown: Complete topdown slots/metrics events check Dapeng Mi
2024-08-12 13:41 ` Arnaldo Carvalho de Melo
2024-08-13 6:54 ` Mi, Dapeng
2024-08-15 6:42 ` Mi, Dapeng
2024-07-12 17:03 ` [Patch v3 2/5] perf x86/topdown: Correct leader selection with sample_read enabled Dapeng Mi
2024-08-12 13:42 ` Arnaldo Carvalho de Melo
2024-08-12 14:37 ` Liang, Kan
2024-08-12 15:18 ` Liang, Kan
2024-08-13 7:15 ` Mi, Dapeng
2024-07-12 17:03 ` [Patch v3 3/5] perf x86/topdown: Don't move topdown metric events in group Dapeng Mi
2024-08-12 15:37 ` Liang, Kan
2024-08-13 7:30 ` Mi, Dapeng
2024-07-12 17:03 ` [Patch v3 4/5] perf tests: Add leader sampling test in record tests Dapeng Mi
2024-07-12 17:03 ` [Patch v3 5/5] perf tests: Add topdown events counting and sampling tests Dapeng Mi
2024-08-12 5:43 ` Mi, Dapeng [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=5de31aa1-8103-4f73-8134-4efe04a73295@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--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 \
--cc=yongwei.ma@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