Prev: HID: Add Support for Setting and Getting Feature Reports from hidraw
Next: USB: gadget: composite: addad disconnect callback
From: Peter Zijlstra on 8 Jun 2010 09:50
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(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: HID: Add Support for Setting and Getting Feature Reports from hidraw
Next: USB: gadget: composite: addad disconnect callback