linux-kernel - Re: [PROPOSAL - FIRST POST] NMI & register clash handling infrastructure

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1276004792.2987.225.camel@twins>
Date:	Tue, 08 Jun 2010 15:46:32 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Oza Oza <ozaoza1982@...oo.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PROPOSAL - FIRST POST] NMI & register clash handling
 infrastructure

On Tue, 2010-06-08 at 14:34 +0530, Oza Oza wrote:


> My proposal/idea/thinking is; 
> have a kernel module which accepts NMI registration from any kernel component, and providing support to the the any kernel service which basically need to service NMI.
> It may not only supports this, but also can provide central infrastructure which has capabilities such as granting MSR (model specific register) access to the the modules, which may avoid potential clash of MSRs (e.g. two modules are trying to configure same MSR), control NMI registration-unregisteration events etc..

We have such a thing, look at register_die_notifier() users, you want to
register for the DIE_NMI notifier.

In fact, if you'd have read the oprofile code, you'd have encountered
these.
--
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/