From: Gabriel Paubert <paubert@iram.es>
To: Hans-Georg Thien <1682-600@onlinehome.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: getting timestamp of last interrupt?
Date: Mon, 6 Oct 2003 17:26:32 +0200 [thread overview]
Message-ID: <20031006152632.GA3419@iram.es> (raw)
In-Reply-To: <3F7E46EE.1020201@onlinehome.de>
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
next prev parent reply other threads:[~2003-10-06 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fj0euih.s2sbop@ifi.uio.no>
[not found] ` <fa.fvjdidn.13ni70f@ifi.uio.no>
2003-10-04 4:03 ` getting timestamp of last interrupt? Hans-Georg Thien
2003-10-06 12:52 ` Richard B. Johnson
2003-10-06 18:21 ` Hans-Georg Thien
2003-10-06 18:34 ` Richard B. Johnson
2003-10-06 19:05 ` Hans-Georg Thien
2003-10-06 19:33 ` Richard B. Johnson
2003-10-06 21:59 ` Hans-Georg Thien
[not found] ` <fa.ch95hks.10kepak@ifi.uio.no>
2003-10-04 4:05 ` Hans-Georg Thien
2003-10-06 15:26 ` Gabriel Paubert [this message]
2003-10-06 18:37 ` Hans-Georg Thien
2003-05-01 21:48 [RFC][PATCH] "Disable Trackpad while typing" on Notebooks withh a PS/2 Trackpad Hans-Georg Thien
2003-05-08 19:12 ` [RFC][PATCH] "Disable Trackpad while typing" on Notebooks withh aPS/2 Trackpad Khalid Aziz
2003-05-27 20:47 ` Hans-Georg Thien
2003-05-27 21:10 ` wwp
2003-10-02 17:40 ` getting timestamp of last interrupt? Hans-Georg Thien
2003-10-02 18:54 ` Karim Yaghmour
2003-10-02 18:59 ` Richard B. Johnson
2003-10-02 22:46 ` Peter Chubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031006152632.GA3419@iram.es \
--to=paubert@iram.es \
--cc=1682-600@onlinehome.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.