[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170619152410.GC23705@tassilo.jf.intel.com>
Date: Mon, 19 Jun 2017 08:24:10 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Alexey Budankov <alexey.budankov@...ux.intel.com>
Cc: Mark Rutland <mark.rutland@....com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Kan Liang <kan.liang@...el.com>,
Dmitri Prokhorov <Dmitry.Prohorov@...el.com>,
Valery Cherepennikov <valery.cherepennikov@...el.com>,
David Carrillo-Cisneros <davidcc@...gle.com>,
Stephane Eranian <eranian@...gle.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/n] perf/core: addressing 4x slowdown during
per-process profiling of STREAM benchmark on Intel Xeon Phi
> One more:
It may help if you run with KASAN enabled. That often
finds problems earlier.
Also could use ftrace and use ftrace_dump_on_oops to
see the sequence (but that has a lot of overhead
and sometimes hides problems)
-Andi
Powered by blists - more mailing lists