From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: kan.liang@linux.intel.com, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, linux-kernel@vger.kernel.org,
dapeng1.mi@linux.intel.com, thomas.falcon@intel.com
Subject: Re: [PATCH V3 0/5] Support auto counter reload
Date: Mon, 3 Mar 2025 18:33:23 -0800 [thread overview]
Message-ID: <Z8ZmcyJl_otpzRgX@tassilo> (raw)
In-Reply-To: <CABPqkBQcKgsrVD+MLYrgiemc2_THOGKi+E1YayFw_pT4VQWGEQ@mail.gmail.com>
> > the branch-instructions is overflowed. So the "cause" event is the
> > branch-instructions event. The acr_mask is set to 0x2, since the
> > event index of branch-instructions is 1.
> >
> What is your definition of 'event index' here? Is it the position on
> the cmdline?
It's the index into the group.
-Andi
prev parent reply other threads:[~2025-03-04 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 21:17 kan.liang
2025-02-13 21:17 ` [PATCH V3 1/5] perf/x86: Add dynamic constraint kan.liang
2025-02-13 21:17 ` [PATCH V3 2/5] perf/x86/intel: Track the num of events needs late setup kan.liang
2025-02-13 21:17 ` [PATCH V3 3/5] perf: Extend the bit width of the arch-specific flag kan.liang
2025-02-13 21:17 ` [PATCH V3 4/5] perf/x86/intel: Add CPUID enumeration for the auto counter reload kan.liang
2025-02-13 21:17 ` [PATCH V3 5/5] perf/x86/intel: Support " kan.liang
2025-02-26 21:43 ` [PATCH V3 0/5] " Falcon, Thomas
2025-03-04 0:58 ` Stephane Eranian
2025-03-04 2:33 ` Andi Kleen [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=Z8ZmcyJl_otpzRgX@tassilo \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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
all inboxes | Powered by JetHome®