Re: DIE_NMI_IPI to oprofile ?

2007-06-26 Thread Björn Steinbrink
On 2007.06.25 23:51:51 -0700, Amitabha Roy wrote: > Hi > > >From looking at the default_do_nmi code in traps.c it seems that (at > least for the non BSP case, with reason=0) the die notifier chain gets > called with val=DIE_NMI_IPI. > > However in the profile_exceptions_notify_handler we check

DIE_NMI_IPI to oprofile ?

2007-06-26 Thread Amitabha Roy
Hi From looking at the default_do_nmi code in traps.c it seems that (at least for the non BSP case, with reason=0) the die notifier chain gets called with val=DIE_NMI_IPI. However in the profile_exceptions_notify_handler we check for DIE_NMI (and not DIE_NMI_IPI) to decide if we want to cycle

DIE_NMI_IPI to oprofile ?

2007-06-26 Thread Amitabha Roy
Hi From looking at the default_do_nmi code in traps.c it seems that (at least for the non BSP case, with reason=0) the die notifier chain gets called with val=DIE_NMI_IPI. However in the profile_exceptions_notify_handler we check for DIE_NMI (and not DIE_NMI_IPI) to decide if we want to cycle

Re: DIE_NMI_IPI to oprofile ?

2007-06-26 Thread Björn Steinbrink
On 2007.06.25 23:51:51 -0700, Amitabha Roy wrote: Hi From looking at the default_do_nmi code in traps.c it seems that (at least for the non BSP case, with reason=0) the die notifier chain gets called with val=DIE_NMI_IPI. However in the profile_exceptions_notify_handler we check for