From: "Christian Tröster" <please.see.sig@gmx.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Notifying a user space application
Date: Thu, 1 Jul 2004 00:29:05 +0200 [thread overview]
Message-ID: <200407010029.05546.please.see.sig@gmx.de> (raw)
Hi!
I'd like to notify a user space application if an interrupt occurs. I had no
problems to install a custom signal handler but I am not sure what's the best
way to notify the application.
My first idea was to send a signal to the application. But as far as I know
one has to know the pid to send the signal. So I'd need some mechanism to get
this pid - perhaps via a /proc entry. Is this a clean solution?
Another idea was to create a (blocking) character device and have the
application listening on that using select() or something like that. But this
seems to be a little bit bloated just for one signal. :)
Are there any other better ways I am not yet aware of. What do you think?
Bye, Christian
- --
| Mail: c dot troester at gmx dot de | PGP-Id: FA006C74 |
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-30 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 22:29 Christian Tröster [this message]
2004-07-01 6:20 ` Notifying a user space application Stefan Nickl
2004-07-01 12:33 ` Christian Tröster
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=200407010029.05546.please.see.sig@gmx.de \
--to=please.see.sig@gmx.de \
--cc=linuxppc-embedded@lists.linuxppc.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.