Hi Frederic, On Wed, Nov 02, 2011 at 07:42:04AM +0000, Frederic Weisbecker wrote: > On Tue, Nov 01, 2011 at 10:20:04AM -0600, David Ahern wrote: > > Right. Originally it could be enabled/disabled. Right now it cannot be, > > but I believe Frederic is working on making it configurable again. > > > > David > > Yep. Will Deacon is working on making the breakpoints able to process > pure arch informations (ie: without beeing forced to use the perf attr > as a midlayer to define them). > > Once we have that I can seperate the breakpoints implementation from perf > and make it opt-able. How do you foresee kdb fitting into this? I see that currently [on x86] we cook up perf_event structures with a specific overflow handler set. If we want to move this over to using a completely arch-defined structure, then we're going to end up with an overflow handler field in both perf_event *and* the arch-specific structure, which doesn't feel right to me. Of course, if the goal is only to separate ptrace (i.e. user debugging) from the perf dependency then we don't need the overflow handler because we'll always just send SIGTRAP to the current task. Any ideas? Will -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
