From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@kernel.org, mingo@redhat.com, kernel-team@fb.com,
Kan Liang <kan.liang@linux.intel.com>,
Like Xu <like.xu@linux.intel.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>
Subject: Re: [RFC] bpf: lbr: enable reading LBR from tracing bpf programs
Date: Wed, 18 Aug 2021 11:15:44 +0200 [thread overview]
Message-ID: <YRzPwClswwxHXVHe@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210818012937.2522409-1-songliubraving@fb.com>
On Tue, Aug 17, 2021 at 06:29:37PM -0700, Song Liu wrote:
> The typical way to access LBR is via hardware perf_event. For CPUs with
> FREEZE_LBRS_ON_PMI support, PMI could capture reliable LBR. On the other
> hand, LBR could also be useful in non-PMI scenario. For example, in
> kretprobe or bpf fexit program, LBR could provide a lot of information
> on what happened with the function.
>
> In this RFC, we try to enable LBR for BPF program. This works like:
> 1. Create a hardware perf_event with PERF_SAMPLE_BRANCH_* on each CPU;
> 2. Call a new bpf helper (bpf_get_branch_trace) from the BPF program;
> 3. Before calling this bpf program, the kernel stops LBR on local CPU,
> make a copy of LBR, and resumes LBR;
> 4. In the bpf program, the helper access the copy from #3.
>
> Please see tools/testing/selftests/bpf/[progs|prog_tests]/get_call_trace.c
> for a detailed example. Not that, this process is far from ideal, but it
> allows quick prototype of this feature.
>
> AFAICT, the biggest challenge here is that we are now sharing LBR in PMI
> and out of PMI, which could trigger some interesting race conditions.
> However, if we allow some level of missed/corrupted samples, this should
> still be very useful.
>
> Please share your thoughts and comments on this. Thanks in advance!
> +int bpf_branch_record_read(void)
> +{
> + struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> +
> + intel_pmu_lbr_disable_all();
> + intel_pmu_lbr_read();
> + memcpy(this_cpu_ptr(&bpf_lbr_entries), cpuc->lbr_entries,
> + sizeof(struct perf_branch_entry) * x86_pmu.lbr_nr);
> + *this_cpu_ptr(&bpf_lbr_cnt) = x86_pmu.lbr_nr;
> + intel_pmu_lbr_enable_all(false);
> + return 0;
> +}
Urgghhh.. I so really hate BPF specials like this. Also, the PMI race
you describe is because you're doing abysmal layer violations. If you'd
have used perf_pmu_disable() that wouldn't have been a problem.
I'd much rather see a generic 'fake/inject' PMI facility, something that
works across the board and isn't tied to x86/intel.
next prev parent reply other threads:[~2021-08-18 9:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 1:29 [RFC] bpf: lbr: enable reading LBR from tracing bpf programs Song Liu
2021-08-18 3:06 ` kernel test robot
2021-08-18 8:43 ` kernel test robot
2021-08-18 8:43 ` [RFC PATCH] bpf: lbr: __pcpu_scope_bpf_lbr_entries can be static kernel test robot
2021-08-18 9:15 ` Peter Zijlstra [this message]
2021-08-18 16:46 ` [RFC] bpf: lbr: enable reading LBR from tracing bpf programs Song Liu
2021-08-19 11:57 ` Peter Zijlstra
2021-08-19 16:46 ` Song Liu
2021-08-19 18:06 ` Peter Zijlstra
2021-08-19 18:22 ` Song Liu
2021-08-19 18:27 ` Peter Zijlstra
2021-08-19 18:45 ` Song Liu
2021-08-20 7:33 ` Song Liu
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=YRzPwClswwxHXVHe@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexey.budankov@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kernel-team@fb.com \
--cc=like.xu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=songliubraving@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.