[lkml]   [2010]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [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

 \ /
  Last update: 2010-06-08 15:49    [W:0.034 / U:3.936 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site