[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cjjjV0uNCNLohFMFizRxvu2vwJBgE-Cge1Y6F3jDuPLNg@mail.gmail.com>
Date: Fri, 10 Sep 2021 15:40:48 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <ak@...ux.intel.com>,
Ian Rogers <irogers@...gle.com>,
Michael Petlan <mpetlan@...hat.com>
Subject: Re: [PATCH v2] perf/core: Add a new read format to get a number of
lost samples
On Fri, Sep 10, 2021 at 2:42 PM Jiri Olsa <jolsa@...hat.com> wrote:
>
> On Wed, Sep 08, 2021 at 10:24:20AM -0700, Namhyung Kim wrote:
> > Sometimes we want to know an accurate number of samples even if it's
> > lost. Currenlty PERF_RECORD_LOST is generated for a ring-buffer which
> > might be shared with other events. So it's hard to know per-event
> > lost count.
> >
> > Add event->lost_samples field and PERF_FORMAT_LOST to retrieve it from
> > userspace.
>
> hi,
> looks good.. will there be some tools/perf change using this?
Sure, I'll work on the userspace part after this is merged.
I'm thinking about adding LOST_SAMPLES records at the end
of the data section as if they came from the kernel.
Thanks,
Namhyung
Powered by blists - more mailing lists