[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180615081223.GB2458@hirez.programming.kicks-ass.net>
Date: Fri, 15 Jun 2018 10:12:23 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: "Jin, Yao" <yao.jin@...ux.intel.com>
Cc: acme@...nel.org, jolsa@...nel.org, mingo@...hat.com,
alexander.shishkin@...ux.intel.com, me@...ehuey.com,
Linux-kernel@...r.kernel.org, vincent.weaver@...ne.edu,
will.deacon@....com, eranian@...gle.com, namhyung@...nel.org,
ak@...ux.intel.com, kan.liang@...el.com, yao.jin@...el.com
Subject: Re: [PATCH v1 0/2] perf: Drop leaked kernel samples
On Fri, Jun 15, 2018 at 04:01:45PM +0800, Jin, Yao wrote:
> Bring more overhead to kernel if we zero the bits considering the number of
> leaked samples may be not too small?
Keeping the samples at least allows you to know how many samples
happened and such things.
> And the skid information may be interesting (see example of hitting on
> page_fault in previous mail). If we zero it, we will not know.
If you throw them out the window you also don't know, do you?
Powered by blists - more mailing lists