Re: [v2 PATCH 2/2] booke/kprobe: remove unnecessary preempt_enable_no_resched

2011-07-11 Thread tiejun.chen
tiejun.chen wrote: > Ananth N Mavinakayanahalli wrote: >> On Mon, Jul 11, 2011 at 10:39:35AM +0800, Tiejun Chen wrote: >>> When enable CONFIG_PREEMPT we will trigger the following call trace: >>> >>> BUG: scheduling while atomic: swapper/1/0x1000 >>> ... >>> >>> krpobe always goes through the f

Re: [v2 PATCH 2/2] booke/kprobe: remove unnecessary preempt_enable_no_resched

2011-07-11 Thread tiejun.chen
Ananth N Mavinakayanahalli wrote: > On Mon, Jul 11, 2011 at 10:39:35AM +0800, Tiejun Chen wrote: >> When enable CONFIG_PREEMPT we will trigger the following call trace: >> >> BUG: scheduling while atomic: swapper/1/0x1000 >> ... >> >> krpobe always goes through the following path: >> >> program

Re: [v2 PATCH 2/2] booke/kprobe: remove unnecessary preempt_enable_no_resched

2011-07-10 Thread Ananth N Mavinakayanahalli
On Mon, Jul 11, 2011 at 10:39:35AM +0800, Tiejun Chen wrote: > When enable CONFIG_PREEMPT we will trigger the following call trace: > > BUG: scheduling while atomic: swapper/1/0x1000 > ... > > krpobe always goes through the following path: > > program_check_exception() > | >

[v2 PATCH 2/2] booke/kprobe: remove unnecessary preempt_enable_no_resched

2011-07-10 Thread Tiejun Chen
When enable CONFIG_PREEMPT we will trigger the following call trace: BUG: scheduling while atomic: swapper/1/0x1000 ... krpobe always goes through the following path: program_check_exception() | + notify_die(DIE_BPT, "breakpoint",...) | + kprob