From: patchwork-bot+linux-riscv@kernel.org
To: Ian Rogers <irogers@google.com>
Cc: linux-riscv@lists.infradead.org, john.g.garry@oracle.com,
will@kernel.org, james.clark@linaro.org, mike.leach@linaro.org,
leo.yan@linux.dev, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.com, kan.liang@linux.intel.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, chenhuacai@kernel.org,
maobibo@loongson.cn, atrajeev@linux.vnet.ibm.com,
ben717@andestech.com, alexghiti@rivosinc.com,
sandipan.das@amd.com, bgray@linux.ibm.com, xu.yang_2@nxp.com,
ravi.bangoria@amd.com, clement.legoffic@foss.st.com,
yangyicong@hisilicon.com, mhiramat@kernel.org,
dima@secretsauce.net, linux@treblig.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Refactor cpuid and metric table lookup code
Date: Wed, 11 Dec 2024 22:32:49 +0000 [thread overview]
Message-ID: <173395636900.1729195.10506266683827384224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241107162035.52206-1-irogers@google.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Arnaldo Carvalho de Melo <acme@redhat.com>:
On Thu, 7 Nov 2024 08:20:27 -0800 you wrote:
> Xu Yang <xu.yang_2@nxp.com> reported issues with the system metric
> lookup:
> https://lore.kernel.org/linux-perf-users/20241106085441.3945502-1-xu.yang_2@nxp.com/
> These patches remove a lot of the logic relating CPUIDs to PMUs so
> that the PMU isn't part of the question when finding a metric table.
> For time reasons, it doesn't go as far as allowing system metrics
> without a metric table as a metric table is needed for metrics to
> refer to other metrics, and the refactoring of that resolution is a
> hassle.
>
> [...]
Here is the summary with links:
- [v2,1/8] perf jevents: fix breakage when do perf stat on system metric
https://git.kernel.org/riscv/c/4a159e6049f3
- [v2,2/8] perf header: Move is_cpu_online to numa bench
https://git.kernel.org/riscv/c/c6fafe36bab3
- [v2,3/8] perf header: Refactor get_cpuid to take a CPU for ARM
https://git.kernel.org/riscv/c/cec0d6572a44
- [v2,4/8] perf arm64 header: Use cpu argument in get_cpuid
https://git.kernel.org/riscv/c/538737da9625
- [v2,5/8] perf header: Avoid transitive PMU includes
https://git.kernel.org/riscv/c/7463ee17a740
- [v2,6/8] perf header: Pass a perf_cpu rather than a PMU to get_cpuid_str
https://git.kernel.org/riscv/c/494c403ff159
- [v2,7/8] perf jevents: Add map_for_cpu
https://git.kernel.org/riscv/c/0434410fa45c
- [v2,8/8] perf pmu: Move pmu_metrics_table__find and remove ARM override
https://git.kernel.org/riscv/c/8f997865ee9e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-12-11 22:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 16:20 [PATCH v2 0/8] Refactor cpuid and metric table lookup code Ian Rogers
2024-11-07 16:20 ` [PATCH v2 1/8] perf jevents: fix breakage when do perf stat on system metric Ian Rogers
2024-11-07 16:20 ` [PATCH v2 2/8] perf header: Move is_cpu_online to numa bench Ian Rogers
2024-11-07 16:20 ` [PATCH v2 3/8] perf header: Refactor get_cpuid to take a CPU for ARM Ian Rogers
2024-11-07 16:20 ` [PATCH v2 4/8] perf arm64 header: Use cpu argument in get_cpuid Ian Rogers
2024-11-07 16:20 ` [PATCH v2 5/8] perf header: Avoid transitive PMU includes Ian Rogers
2024-11-07 16:20 ` [PATCH v2 6/8] perf header: Pass a perf_cpu rather than a PMU to get_cpuid_str Ian Rogers
2024-11-07 16:20 ` [PATCH v2 7/8] perf jevents: Add map_for_cpu Ian Rogers
2024-11-07 16:20 ` [PATCH v2 8/8] perf pmu: Move pmu_metrics_table__find and remove ARM override Ian Rogers
2024-11-09 10:54 ` Yicong Yang
2024-11-09 16:10 ` Ian Rogers
2024-11-11 8:39 ` Yicong Yang
2024-11-08 2:55 ` [PATCH v2 0/8] Refactor cpuid and metric table lookup code Xu Yang
2024-11-14 18:31 ` Ian Rogers
2024-11-15 15:35 ` James Clark
2024-11-15 15:43 ` Arnaldo Carvalho de Melo
2024-11-16 19:47 ` Arnaldo Carvalho de Melo
2024-12-11 22:32 ` patchwork-bot+linux-riscv [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=173395636900.1729195.10506266683827384224.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=ben717@andestech.com \
--cc=bgray@linux.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=clement.legoffic@foss.st.com \
--cc=dima@secretsauce.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@treblig.org \
--cc=maobibo@loongson.cn \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=sandipan.das@amd.com \
--cc=will@kernel.org \
--cc=xu.yang_2@nxp.com \
--cc=yangyicong@hisilicon.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).