From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: peterz@infradead.org, acme@kernel.org, mingo@redhat.com,
eranian@google.com, mpe@ellerman.id.au,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
andreas.kogler.0x@gmail.com, atrajeev@linux.vnet.ibm.com,
ravi.bangoria@amd.com
Subject: Re: [PATCH 0/6] Add sample_flags to improve the perf_sample_data struct
Date: Thu, 1 Sep 2022 08:47:35 -0400 [thread overview]
Message-ID: <a751a7ea-78b6-d278-4cbb-eef17294fcf3@linux.intel.com> (raw)
In-Reply-To: <Yw/j8rXIRwAnXhy3@google.com>
On 2022-08-31 6:42 p.m., Namhyung Kim wrote:
> (Adding Ravi to CC)
>
> On Wed, Aug 31, 2022 at 07:55:08AM -0700, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> The patch series is to fix PEBS timestamps overwritten and improve the
>> perf_sample_data struct. The detailed discussion can be found at
>> https://lore.kernel.org/lkml/YwXvGe4%2FQdgGYOKJ@worktop.programming.kicks-ass.net/
>>
>> The patch series has two changes compared with the suggestions in the
>> above discussion.
>> - Only clear the sample flags for the perf_prepare_sample().
>> The __perf_event_header__init_id is shared between perf_prepare_sample()
>> (used by PERF_RECORD_SAMPLE) and perf_event_header__init_id() (used by
>> other PERF_RECORD_* event type). The sample data is only available
>> for the PERF_RECORD_SAMPLE.
>> - The CALLCHAIN_EARLY hack is still required for the BPF, especially
>> perf_event_set_bpf_handler(). The sample data is not available when
>> the function is invoked.
>
> In general, looks good! I'd like to work on the BPF side so that it can
> get the sample data for filtering.
Thanks Namhyung. I will send out the V2 shortly. I think the BPF work
can be on top of it.
Thanks,
Kan
> The previous discussion was at
>
> https://lore.kernel.org/all/CAM9d7cjj0X90=NsvdwaLMGCDVkMJBLAGF_q-+Eqj6b44OAnzoQ@mail.gmail.com/
>
> Thanks,
> Namhyung
>
>>
>> Kan Liang (6):
>> perf: Add sample_flags to indicate the PMU-filled sample data
>> perf/x86/intel/pebs: Fix PEBS timestamps overwritten
>> perf: Use sample_flags for branch stack
>> perf: Use sample_flags for weight
>> perf: Use sample_flags for data_src
>> perf: Use sample_flags for txn
>>
>> arch/powerpc/perf/core-book3s.c | 10 ++++++---
>> arch/x86/events/core.c | 4 +++-
>> arch/x86/events/intel/core.c | 4 +++-
>> arch/x86/events/intel/ds.c | 39 ++++++++++++++++++++++++---------
>> include/linux/perf_event.h | 15 ++++++-------
>> kernel/events/core.c | 33 +++++++++++++++++++---------
>> 6 files changed, 72 insertions(+), 33 deletions(-)
>>
>> --
>> 2.35.1
>>
>>
next prev parent reply other threads:[~2022-09-01 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 14:55 [PATCH 0/6] Add sample_flags to improve the perf_sample_data struct kan.liang
2022-08-31 14:55 ` [PATCH 1/6] perf: Add sample_flags to indicate the PMU-filled sample data kan.liang
2022-08-31 14:55 ` [PATCH 2/6] perf/x86/intel/pebs: Fix PEBS timestamps overwritten kan.liang
2022-08-31 14:55 ` [PATCH 3/6] perf: Use sample_flags for branch stack kan.liang
2022-08-31 22:47 ` Namhyung Kim
2022-09-01 12:42 ` Liang, Kan
2022-08-31 14:55 ` [PATCH 4/6] perf: Use sample_flags for weight kan.liang
2022-08-31 14:55 ` [PATCH 5/6] perf: Use sample_flags for data_src kan.liang
2022-08-31 14:55 ` [PATCH 6/6] perf: Use sample_flags for txn kan.liang
2022-08-31 22:42 ` [PATCH 0/6] Add sample_flags to improve the perf_sample_data struct Namhyung Kim
2022-09-01 12:47 ` Liang, Kan [this message]
2022-09-02 5:24 ` Namhyung Kim
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=a751a7ea-78b6-d278-4cbb-eef17294fcf3@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andreas.kogler.0x@gmail.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.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