Oleg Nesterov 1b08e90721 uprobes: Kill UTASK_BP_HIT state ... Kill UTASK_BP_HIT state, it buys nothing but complicates the code. It is only used in uprobe_notify_resume() to decide who should be called, we can check utask->active_uprobe != NULL instead. And this allows us to simplify handle_swbp(), no need to clear utask->state. Likewise we could kill UTASK_SSTEP, but UTASK_BP_HIT is worse and imho should die. The problem is, it creates the special case when task->utask is NULL, we can't distinguish RUNNING and BP_HIT. With this patch utask == NULL always means RUNNING. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>		2012-09-29 21:21:53 +02:00
..
callchain.c	perf: Add attribute to filter out callchains	2012-08-10 12:40:57 -03:00
core.c	perf: Add ability to attach user stack dump to sample	2012-08-10 12:17:58 -03:00
hw_breakpoint.c	Merge branch 'x86/cleanups' into perf/uprobes	2012-03-13 16:33:03 +01:00
internal.h	perf: Add ability to attach user stack dump to sample	2012-08-10 12:17:58 -03:00
Makefile	uprobes: Move to kernel/events/	2012-02-22 11:08:00 +01:00
ring_buffer.c	perf: Add perf_output_skip function to skip bytes in sample	2012-08-10 12:16:22 -03:00
uprobes.c	uprobes: Kill UTASK_BP_HIT state	2012-09-29 21:21:53 +02:00