From: Ingo Molnar <mingo@kernel.org>
To: kan.liang@linux.intel.com
Cc: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, dapeng1.mi@linux.intel.com,
zhenyuw@linux.intel.com
Subject: Re: [PATCH 0/6] Cleanup Intel PMU initialization code
Date: Tue, 29 Aug 2023 20:59:56 +0200 [thread overview]
Message-ID: <ZO5ALPl/Li+Fr1SC@gmail.com> (raw)
In-Reply-To: <20230829125806.3016082-1-kan.liang@linux.intel.com>
* kan.liang@linux.intel.com <kan.liang@linux.intel.com> wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> The patch set is to clean up the Intel PMU initialization code. There is
> no functional change.
>
> Kan Liang (6):
> perf/x86/intel: Use the common uarch name for the shared functions
> perf/x86/intel: Factor out the initialization code for SPR
> perf/x86/intel: Factor out the initialization code for ADL e-core
> perf/x86/intel: Apply the common initialization code for ADL
> perf/x86/intel: Cleanup the hybrid CPU type
> perf/x86/intel: Add common intel_pmu_init_hybrid
>
> arch/x86/events/core.c | 6 +-
> arch/x86/events/intel/core.c | 397 ++++++++++++++++++-----------------
> arch/x86/events/intel/ds.c | 4 +-
> arch/x86/events/perf_event.h | 37 ++--
> 4 files changed, 226 insertions(+), 218 deletions(-)
Applied, thanks.
Ingo
prev parent reply other threads:[~2023-08-29 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 12:58 [PATCH 0/6] Cleanup Intel PMU initialization code kan.liang
2023-08-29 12:58 ` [PATCH 1/6] perf/x86/intel: Use the common uarch name for the shared functions kan.liang
2023-08-29 19:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-08-29 12:58 ` [PATCH 2/6] perf/x86/intel: Factor out the initialization code for SPR kan.liang
2023-08-29 19:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-08-29 12:58 ` [PATCH 3/6] perf/x86/intel: Factor out the initialization code for ADL e-core kan.liang
2023-08-29 19:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-08-29 12:58 ` [PATCH 4/6] perf/x86/intel: Apply the common initialization code for ADL kan.liang
2023-08-29 19:31 ` [tip: perf/core] " tip-bot2 for Kan Liang
2023-08-29 12:58 ` [PATCH 5/6] perf/x86/intel: Cleanup the hybrid CPU type kan.liang
2023-08-29 19:31 ` [tip: perf/core] perf/x86/intel: Clean up the hybrid CPU type handling code tip-bot2 for Kan Liang
2023-08-29 12:58 ` [PATCH 6/6] perf/x86/intel: Add common intel_pmu_init_hybrid kan.liang
2023-08-29 19:31 ` [tip: perf/core] perf/x86/intel: Add common intel_pmu_init_hybrid() tip-bot2 for Kan Liang
2023-08-29 18:59 ` Ingo Molnar [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=ZO5ALPl/Li+Fr1SC@gmail.com \
--to=mingo@kernel.org \
--cc=dapeng1.mi@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=zhenyuw@linux.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