From: Hans-Georg Thien <1682-600@onlinehome.de>
To: linux-kernel@vger.kernel.org
Subject: Re: getting timestamp of last interrupt?
Date: Sat, 04 Oct 2003 06:03:55 +0200 [thread overview]
Message-ID: <3F7E46AB.3030709@onlinehome.de> (raw)
In-Reply-To: <fa.fvjdidn.13ni70f@ifi.uio.no>
Richard B. Johnson wrote:
> On Thu, 2 Oct 2003, 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?
>
>
> You can get A SIGIO signal for every keyboard, (or other input) event.
> What you do with it is entirely up to you. Linux/Unix doesn't have
> "callbacks", instead it has signals. It also has select() and poll(),
> all useful for handling such events. If you want a time-stamp, you
> call gettimeofday() in your signal handler.
>
Thanks a lot Richard,
... but ... can I use signals in kernel mode?
next parent reply other threads:[~2003-10-04 4:03 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 ` Hans-Georg Thien [this message]
2003-10-06 12:52 ` getting timestamp of last interrupt? 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
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=3F7E46AB.3030709@onlinehome.de \
--to=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.