From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
irogers@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/5] Several fixes for group flag and counters-snapshotting
Date: Fri, 25 Apr 2025 14:55:56 +0200 [thread overview]
Message-ID: <20250425125556.GD22125@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <c919a36c-f343-48ce-a262-401159c5bf30@linux.intel.com>
On Thu, Apr 24, 2025 at 12:00:02PM -0400, Liang, Kan wrote:
>
>
> On 2025-04-24 10:25 a.m., Peter Zijlstra wrote:
> > On Thu, Apr 24, 2025 at 06:47:13AM -0700, kan.liang@linux.intel.com wrote:
> >> From: Kan Liang <kan.liang@linux.intel.com>
> >>
> >> The patch series includes several fixes for the new Intel features.
> >>
> >> The first 4 patches are to fix the group flag issue which impacts the
> >> branch counters, PEBS counters-snapshotting and ACR.
> >> The V1 can be found at
> >> https://lore.kernel.org/lkml/20250423221015.268949-1-kan.liang@linux.intel.com/
> >>
> >> The last patch is to fix an issue of counters-snapshotting.
> >> The V1 can be found at
> >> https://lore.kernel.org/lkml/20250204210514.4089680-1-kan.liang@linux.intel.com/
> >>
> >> Kan Liang (5):
> >> perf/x86/intel: Only check the group flag for X86 leader
> >> perf/x86/intel: Check the X86 leader for pebs_counter_event_group
> >> perf/x86/intel: Check the X86 leader for ACR group
> >> perf/x86: Optimize the is_x86_event
> >> perf/x86/intel/ds: Fix counter backwards of non-precise events
> >> counters-snapshotting
> >
> > It didn't apply cleanly,
>
> Sorry for it.
>
> > but I stomped on it and pushed out new
> > perf/urgent and perf/core branches that contain these patches. Hopefully
> > I didn't mess it up ;-)
>
> Something is missed in this patch 5d4d71ebc737 ("perf/x86/intel: Only
> check the group flag for X86 leader")
>
> diff --git a/arch/x86/events/perf_event.h b/arch/x86/events/perf_event.h
> index a73b1ff031b2..1f72a4f77b5c 100644
> --- a/arch/x86/events/perf_event.h
> +++ b/arch/x86/events/perf_event.h
> @@ -119,7 +119,7 @@ static inline bool check_leader_group(struct
> perf_event *leader, int flags)
>
> static inline bool is_branch_counters_group(struct perf_event *event)
> {
> - return check_leader_group(event->group_leader, PERF_X86_EVENT_PEBS_CNTR);
> + return check_leader_group(event->group_leader,
> PERF_X86_EVENT_BRANCH_COUNTERS);
> }
>
> static inline bool is_pebs_counter_event_group(struct perf_event *event)
Right.
> @@ -1123,7 +1123,6 @@ static struct perf_pmu_format_hybrid_attr
> format_attr_hybrid_##_name = {\
> .pmu_type = _pmu, \
> }
>
> -int is_x86_event(struct perf_event *event);
> struct pmu *x86_get_pmu(unsigned int cpu);
> extern struct x86_pmu x86_pmu __read_mostly;
See, that isn't there in tip/perf/urgent :-)
I've pushed out an updated set. Please check.
next prev parent reply other threads:[~2025-04-25 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 13:47 [PATCH V2 0/5] Several fixes for group flag and counters-snapshotting kan.liang
2025-04-24 13:47 ` [PATCH V2 1/5] perf/x86/intel: Only check the group flag for X86 leader kan.liang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-04-24 13:47 ` [PATCH V2 2/5] perf/x86/intel: Check the X86 leader for pebs_counter_event_group kan.liang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-04-24 13:47 ` [PATCH V2 3/5] perf/x86/intel: Check the X86 leader for ACR group kan.liang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-04-24 13:47 ` [PATCH V2 4/5] perf/x86: Optimize the is_x86_event kan.liang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-04-24 13:47 ` [PATCH V2 5/5] perf/x86/intel/ds: Fix counter backwards of non-precise events counters-snapshotting kan.liang
2025-04-30 11:58 ` [tip: perf/core] " tip-bot2 for Kan Liang
2025-04-24 14:25 ` [PATCH V2 0/5] Several fixes for group flag and counters-snapshotting Peter Zijlstra
2025-04-24 16:00 ` Liang, Kan
2025-04-25 12:55 ` Peter Zijlstra [this message]
2025-04-25 13:54 ` 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=20250425125556.GD22125@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox