Messages in this thread | | | From | Gabriel Paubert <> | Date | Mon, 6 Oct 2003 17:26:32 +0200 | Subject | Re: getting timestamp of last interrupt? |
| |
On Sat, Oct 04, 2003 at 06:05:02AM +0200, Hans-Georg Thien wrote: > Karim Yaghmour wrote: > > > > >Hans-Georg Thien wrote: > > > >>I am looking for a possibility to read out the last timestamp when an > >>interrupt has occured. > >> > >>e.g.: the user presses a key on the keyboard. Where can I read out the > >>timestamp of this event? > >> > >>To be more precise, I 'm looking for > >> > >>( )a function call > >>( ) a callback where I can register to be notified when an event occurs > >>( ) a global accessible variable > >>( ) a /proc entry > >> > >>or something like that. > >> > >>Any ideas ? > > > > > >Have a look at the Linux Trace Toolkit: > >http://www.opersys.com/LTT/ > >It records micro-second time-stamps for quite a few events, including > >interrupts. > > > thanke a lot for reply Karim, > > but I think that LTT does not fit to my needs. It needs to modify the > kernel - and that is what I want to avoid. > > I'm looking for a already existing built-in capability. > > Maybe signal SIGIO is a solution, if it does not > > (x) give me *every* IO event > (x) has to much overhead - I have to respond to keyboard/mouse events, *not*
Doesn't the input layer add a timestamp to every event?
At least that's the impression I have from xxd /dev/input/eventN: the first eight bytes of each 16 bytes packet look so furiously close to a struct timeval that they can't be anything else :-)
Just that I don't know how the devices and N are associated, it seems to be order of discovery/registering at boot.
Regards, Gabriel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |