From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: "open list:BPF (Safe dynamic programs and tools)"
<bpf@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
Kernel Team <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: Thu, 19 Aug 2021 20:27:19 +0200 [thread overview]
Message-ID: <YR6ih+pKSm5TVVBc@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <A5F7CF90-27F9-476C-B87C-CAD2A6BE5DA4@fb.com>
On Thu, Aug 19, 2021 at 06:22:07PM +0000, Song Liu wrote:
> > And if we're going to be adding new pmu::methods then I figure one that
> > does the whole sample state might be more useful.
>
> What do you mean by "whole sample state"? To integrate with exiting
> perf_sample_data, like perf_output_sample()?
Yeah, the PMI can/does set more than data->br_stack, but I'm now
thinking that without an actual PMI, much of that will not be possible.
br_stack is special here.
Oh well, carry on I suppose.
next prev parent reply other threads:[~2021-08-19 18:27 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 ` [RFC] bpf: lbr: enable reading LBR from tracing bpf programs Peter Zijlstra
2021-08-18 16:46 ` 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 [this message]
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=YR6ih+pKSm5TVVBc@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=alexey.budankov@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=kan.liang@linux.intel.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.