DIE_NMI_IPI to oprofile ?

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 ?

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

[patch 1/1] oprofile: Add a special cookie for the VDSO region

Emit a special VDSO_COOKIE for VDSO regions instead of simply marking them as anon. Signed-off-by: Amitabha Roy <[EMAIL PROTECTED]> --- diff --git a/drivers/oprofile/buffer_sync.c b/drivers/oprofile/buffer_sync.c index 78c2e6e..7f879db 100644 --- a/drivers/oprofile/buffer_sync.c +++ b/d

[patch 1/1] oprofile: Add a special cookie for the VDSO region

Emit a special VDSO_COOKIE for VDSO regions instead of simply marking them as anon. Signed-off-by: Amitabha Roy [EMAIL PROTECTED] --- diff --git a/drivers/oprofile/buffer_sync.c b/drivers/oprofile/buffer_sync.c index 78c2e6e..7f879db 100644 --- a/drivers/oprofile/buffer_sync.c +++ b/drivers