The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Sanil K <Sanil.K@lntinfotech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interrupt handling
Date: Thu, 16 Oct 2003 11:53:18 -0700	[thread overview]
Message-ID: <3F8EE91E.5090202@mvista.com> (raw)
In-Reply-To: <OF7678B59D.AD894507-ON65256DC1.0048458F@lntinfotech.com>

Sanil K wrote:
> Hi all,
> 
> This may be a generic problem as far as a driver is concerned.
> 
> We need to handle an interrupt and inform the user space on the event and
> pass the data correspodning to the event.
> 
> The event can be informed through SIGNAL and the signal handler can be
> invoked in the user space. Then again for data, we need to have the
> "copy_to_user" mechanism .
> 
> Is there any other effective mechanism(s) to handle the interrupt. I mean
> we need to convey the event and or data to the user space(prefer -
> asynchronously).
> 
IF the amount of data is small, say a word or two or less, you can use the 
siginfo and a realtime signal.  This will get the data at the same time as the 
signal.  If you prefer to avoid the overhead of the signal, you can do 
sigwaitinfo() which avoids the floating point save/restore, but does require the 
task to wait (i.e. is not asynchronous).




-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2003-10-16 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 13:16 Interrupt handling Sanil K
2003-10-16 13:51 ` Richard B. Johnson
2003-10-16 19:55   ` Maciej Zenczykowski
2003-10-16 20:10     ` Richard B. Johnson
2003-10-16 18:53 ` George Anzinger [this message]
2003-10-16 19:08 ` Tom Zanussi

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=3F8EE91E.5090202@mvista.com \
    --to=george@mvista.com \
    --cc=Sanil.K@lntinfotech.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox