[lkml]   [2010]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PROPOSAL - FIRST POST] NMI & register clash handling infrastructure

This is my first post to the group, please excuse me, If I unknowingly miss to follow writing ethics.


I was working on providing accurate process usage support, and writing a kernel module,
I configured cpu-core-unhalted-event and configured LVT (local vector table) with NMI (non-maskable interrupt), and surprisingly Oprofile stopped working,
Then I realized, that set_nmi_call back just overwrites nmi_callback function pointer.

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..

I am not sure, whether this is a good idea or bad idea, but I thought it adds flexibility and some value addition in kernel,
and I find this place precisely right to post this idea.

Any feedback/suggestions/additions would be appreciated.


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