From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, namhyung@kernel.org, irogers@google.com,
adrian.hunter@intel.com, ak@linux.intel.com, eranian@google.com,
alexey.v.bayduraev@linux.intel.com, tinghao.zhang@intel.com
Subject: Re: [PATCH V4 4/7] perf/x86/intel: Support LBR event logging
Date: Thu, 19 Oct 2023 10:31:49 -0400 [thread overview]
Message-ID: <9d388599-8c7b-4461-be05-76a8b452fd26@linux.intel.com> (raw)
In-Reply-To: <20231019110917.GI36211@noisy.programming.kicks-ass.net>
On 2023-10-19 7:09 a.m., Peter Zijlstra wrote:
> On Wed, Oct 04, 2023 at 11:40:41AM -0700, kan.liang@linux.intel.com wrote:
>
>> @@ -3905,6 +3915,44 @@ static int intel_pmu_hw_config(struct perf_event *event)
>> if (needs_branch_stack(event) && is_sampling_event(event))
>> event->hw.flags |= PERF_X86_EVENT_NEEDS_BRANCH_STACK;
>>
>> + if (branch_sample_counters(event)) {
>> + struct perf_event *leader, *sibling;
>> +
>> + if (!(x86_pmu.flags & PMU_FL_LBR_EVENT) ||
>> + (event->attr.config & ~INTEL_ARCH_EVENT_MASK))
>> + return -EINVAL;
>> +
>> + /*
>> + * The event logging is not supported in the call stack mode
>> + * yet, since we cannot simply flush the LBR during e.g.,
>> + * multiplexing. Also, there is no obvious usage with the call
>> + * stack mode. Simply forbids it for now.
>> + *
>> + * If any events in the group enable the LBR event logging
>> + * feature, the group is treated as a LBR event logging group,
>> + * which requires the extra space to store the counters.
>> + */
>> + leader = event->group_leader;
>> + if (branch_sample_call_stack(leader))
>> + return -EINVAL;
>> + leader->hw.flags |= PERF_X86_EVENT_BRANCH_COUNTERS;
>
> (superfluous whitespace before operator)
>
>> +
>> + for_each_sibling_event(sibling, leader) {
>> + if (branch_sample_call_stack(sibling))
>> + return -EINVAL;
>> + }
>> +
>> + /*
>> + * Only applying the PERF_SAMPLE_BRANCH_COUNTERS doesn't
>> + * require any branch stack setup.
>> + * Clear the bit to avoid unnecessary branch stack setup.
>> + */
>> + if (0 == (event->attr.branch_sample_type &
>> + ~(PERF_SAMPLE_BRANCH_PLM_ALL |
>> + PERF_SAMPLE_BRANCH_COUNTERS)))
>> + event->hw.flags &= ~PERF_X86_EVENT_NEEDS_BRANCH_STACK;
>> + }
>
> Does this / should this check the number of group members vs supported
> number of lbr counters?
Sure, I will add the check here for the numbers, so perf can error out
earlier.
Thanks,
Kan
next prev parent reply other threads:[~2023-10-19 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 18:40 [PATCH V4 1/7] perf: Add branch stack counters kan.liang
2023-10-04 18:40 ` [PATCH V4 2/7] perf/x86: Add PERF_X86_EVENT_NEEDS_BRANCH_STACK flag kan.liang
2023-10-04 18:40 ` [PATCH V4 3/7] perf: Add branch_sample_call_stack kan.liang
2023-10-04 18:40 ` [PATCH V4 4/7] perf/x86/intel: Support LBR event logging kan.liang
2023-10-19 9:23 ` Peter Zijlstra
2023-10-19 13:56 ` Liang, Kan
2023-10-19 9:26 ` Peter Zijlstra
2023-10-19 13:58 ` Liang, Kan
2023-10-19 10:52 ` Peter Zijlstra
2023-10-19 14:26 ` Liang, Kan
2023-10-19 18:18 ` Peter Zijlstra
2023-10-19 11:00 ` Peter Zijlstra
2023-10-19 14:28 ` Liang, Kan
2023-10-19 11:09 ` Peter Zijlstra
2023-10-19 14:31 ` Liang, Kan [this message]
2023-10-19 11:12 ` Peter Zijlstra
2023-10-20 12:45 ` Liang, Kan
2023-10-04 18:40 ` [PATCH V4 5/7] tools headers UAPI: Sync include/uapi/linux/perf_event.h header with the kernel kan.liang
2023-10-04 18:40 ` [PATCH V4 6/7] perf header: Support num and width of branch counters kan.liang
2023-10-04 18:40 ` [PATCH V4 7/7] perf tools: Add branch counter knob kan.liang
2023-10-16 17:48 ` [PATCH V4 1/7] perf: Add branch stack counters 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=9d388599-8c7b-4461-be05-76a8b452fd26@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.v.bayduraev@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tinghao.zhang@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
Powered by JetHome