mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Melo <arnaldo.melo@gmail.com>
To: linux-perf-users@vger.kernel.org, Ian Rogers <irogers@google.com>,
	Samuel Wu <wusamuel@google.com>
Cc: Lalit Maganti <lalitmaganti@gmail.com>,
	acme@kernel.org, namhyung@kernel.org, james.clark@linaro.org,
	adrian.hunter@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf python: Accept events larger than union perf_event
Date: Mon, 09 Nov 2026 17:02:11 -0300	[thread overview]
Message-ID: <BCA0C66E-7AF5-4368-AAE3-FB96B09712A6@gmail.com> (raw)
In-Reply-To: <CAP-5=fX6aqHuaV5c+Kfk5iY7SWgXKu+kWX+ReQ4agqkHg89tUA@mail.gmail.com>



On November 9, 2026 3:27:56 PM GMT-03:00, Ian Rogers <irogers@google.com> wrote:
>On Mon, Nov 9, 2026 at 9:58 AM Samuel Wu <wusamuel@google.com> wrote:
>>
>> On Sun, Oct 18, 2026 at 12:45 AM Lalit Maganti <lalitmaganti@gmail.com> wrote:
>> >
>> > Samples recorded with --call-graph dwarf carry a copy of the user stack
>> > and are larger than union perf_event, so session.process_events()
>> > fails on the first one:
>> >
>> >   $ perf record --call-graph dwarf -- ./workload
>> >   $ python3 tools/perf/python/stackcollapse.py
>> >   ...
>> >   TypeError: Unexpected event size: 4168 < 8424
>> >
>> > This makes all the standalone scripts unusable on such recordings.
>> >
>> > pyrf_event__new() rejects events larger than union perf_event, which
>> > guarded the copy into the union that pyrf_event used to embed. Since
>> > commit 2c672ffdad4b ("perf python: Lazily copy events and samples from
>> > process_events") the event is borrowed, or copied to a buffer of
>> > header.size bytes when a callback keeps it, so nothing depends on the
>> > event fitting in the union any more. Remove the check.
>> >
>> > With this, stackcollapse.py and flamegraph.py process a DWARF recording
>> > of a two-thread workload, with the same per-symbol sample counts as
>> > perf script, also when the callback keeps the events after returning.
>> >
>> > Assisted-by: LLM
>> > Signed-off-by: Lalit Maganti <lalitmaganti@gmail.com>
>
>Probably worth having:
>
>Fixes: 2c672ffdad4b ("perf python: Lazily copy events and samples from
>process_events")
>
>Reviewed-by: Ian Rogers <irogers@google.com>


I'll pick it for v7.4,

Thanks,

- Arnaldo 
>
>Thanks,
>Ian
>
>> > ---
>> >  tools/perf/util/python.c | 5 -----
>> >  1 file changed, 5 deletions(-)
>> >
>> > diff --git a/tools/perf/util/python.c b/tools/perf/util/python.c
>> > index 60dbe2dad5eb..8b4b2f3d0926 100644
>> > --- a/tools/perf/util/python.c
>> > +++ b/tools/perf/util/python.c
>> > @@ -1792,11 +1792,6 @@ static PyObject *pyrf_event__new(const union perf_event *event, struct evsel *ev
>> >                                     event->header.size, event->header.type);
>> >         }
>> >
>> > -       if (event->header.size > sizeof(union perf_event)) {
>> > -               return PyErr_Format(PyExc_TypeError, "Unexpected event size: %zu < %u",
>> > -                                   sizeof(union perf_event), event->header.size);
>> > -       }
>> > -
>> >         pevent = PyObject_New(struct pyrf_event, pyrf_event__type[event->header.type]);
>> >         if (pevent == NULL)
>> >                 return PyErr_NoMemory();
>> >
>> > base-commit: 1c90f0a3c8a1c4e38f9edd97af9e20848805a7fb
>> > --
>> > 2.56.0
>> >
>>
>> Reviewed-by: Samuel Wu <wusamuel@google.com>
>

- Arnaldo

      reply	other threads:[~2026-11-09 20:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  7:45 Lalit Maganti
2026-11-09 17:58 ` Samuel Wu
2026-11-09 18:27   ` Ian Rogers
2026-11-09 20:02     ` Arnaldo Melo [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=BCA0C66E-7AF5-4368-AAE3-FB96B09712A6@gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=lalitmaganti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=wusamuel@google.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®