[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160324104244.GP6356@twins.programming.kicks-ass.net>
Date: Thu, 24 Mar 2016 11:42:44 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Will Deacon <will.deacon@....com>
Cc: Wang Nan <wangnan0@...wei.com>, mingo@...hat.com,
linux-kernel@...r.kernel.org, He Kuang <hekuang@...wei.com>,
Alexei Starovoitov <ast@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Brendan Gregg <brendan.d.gregg@...il.com>,
Jiri Olsa <jolsa@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Zefan Li <lizefan@...wei.com>, pi3orama@....com
Subject: Re: [PATCH 2/5] perf core: Set event's default overflow_handler
On Thu, Mar 24, 2016 at 09:58:02AM +0000, Will Deacon wrote:
> On Wed, Mar 23, 2016 at 08:29:38PM +0100, Peter Zijlstra wrote:
> Not sure... I can imagine kgdb, for example, wanting to handle the stepping
> itself. You also need to play clever tricks if you want to step through
> LL/SC atomics, which the code here doesn't even try to handle (because
> it involves disassembling the instructions and applying a bunch of
> heuristics), so I imagine most debuggers wanting to take care of the step
> themselves.
Fair enough... right, a whole host of tricky this.
Powered by blists - more mailing lists