From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, irogers@google.com,
linux-kernel@vger.kernel.org
Cc: Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH V2 3/5] perf/x86/intel: Check the X86 leader for ACR group
Date: Thu, 24 Apr 2025 06:47:16 -0700 [thread overview]
Message-ID: <20250424134718.311934-4-kan.liang@linux.intel.com> (raw)
In-Reply-To: <20250424134718.311934-1-kan.liang@linux.intel.com>
From: Kan Liang <kan.liang@linux.intel.com>
The auto counter reload group also requires a group flag in the leader.
The leader must be a X86 event.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
---
arch/x86/events/perf_event.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/events/perf_event.h b/arch/x86/events/perf_event.h
index fd409d70e568..bac252ba3da6 100644
--- a/arch/x86/events/perf_event.h
+++ b/arch/x86/events/perf_event.h
@@ -129,7 +129,7 @@ static inline bool is_pebs_counter_event_group(struct perf_event *event)
static inline bool is_acr_event_group(struct perf_event *event)
{
- return event->group_leader->hw.flags & PERF_X86_EVENT_ACR;
+ return check_leader_group(event->group_leader, PERF_X86_EVENT_ACR);
}
struct amd_nb {
--
2.38.1
next prev parent reply other threads:[~2025-04-24 13:47 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 ` kan.liang [this message]
2025-04-30 11:58 ` [tip: perf/core] perf/x86/intel: Check the X86 leader for ACR group 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
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=20250424134718.311934-4-kan.liang@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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