From: David Hawkins <dwh@ovro.caltech.edu>
To: Mirek23 <miroslaw.dach@psi.ch>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: signals handling in the kernel
Date: Tue, 07 Aug 2007 09:54:33 -0700 [thread overview]
Message-ID: <46B8A3C9.7060806@ovro.caltech.edu> (raw)
In-Reply-To: <12032525.post@talk.nabble.com>
Hi Mirek,
> I would like to send signals from the interrupt handler
> routine (in the kernel) to the user application (in user space).
> I have googled on that net and I have found that it could be done with the
> function: kill_proc_info.
Look in Rubini for the section regarding asynchronous
notification, Ch 6.
The callback to generate SIGIO is fasync.
Cheers
Dave
next prev parent reply other threads:[~2007-08-07 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 11:32 signals handling in the kernel Mirek23
2007-08-07 16:54 ` David Hawkins [this message]
2007-08-07 18:31 ` David Hawkins
2007-08-08 7:32 ` Mirek23
2007-08-08 17:19 ` David Hawkins
2007-08-30 15:23 ` Mirek23
2007-08-30 15:57 ` David Hawkins
2007-08-08 8:15 ` Mirek23
2007-08-09 13:47 ` Detlev Zundel
2007-08-20 11:49 ` Mirek23
2007-08-20 16:53 ` David Hawkins
2007-08-23 10:57 ` Mirek23
2007-08-23 16:32 ` David Hawkins
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=46B8A3C9.7060806@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miroslaw.dach@psi.ch \
/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.