linux-kernel - DIE_NMI_IPI to oprofile ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <cf9d85500706252351k68924882s2c6bc58454d1bb9b@mail.gmail.com>
Date:	Mon, 25 Jun 2007 23:51:51 -0700
From:	"Amitabha Roy" <amitabha.roy@...il.com>
To:	oprofile-list@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: 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 through the
counters. This seems wrong to me unless I am missing something (which
must be the case, otherwise this code is broken :).

Can anyone help me understand this ?

Thanks
-Amitabha
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/