From: Detlev Zundel <dzu@denx.de>
To: linuxppc-embedded@ozlabs.org
Cc: Mirek23 <miroslaw.dach@psi.ch>
Subject: Re: signals handling in the kernel
Date: Thu, 09 Aug 2007 15:47:12 +0200 [thread overview]
Message-ID: <m2ps1wyg4f.fsf@ohwell.denx.de> (raw)
In-Reply-To: 12048974.post@talk.nabble.com
Hi Miroslaw,
> I did not find however what would be the best way to propagate interrupt
> signals to the USER level / notify the client that interrupt has occurred.
Follow the advice given here before (and in the book you mention), and
implement poll() in the driver and use select() from userspace to
react to it. That's the natural solution in the Unix context for what
you are trying to do. It is not a coincidence that I can only find 3
references to kill_proc below drivers/.
Of course you are welcome to solve your actual problem (using
kill_proc like e.g. drivers/char/watchdog/wd.c) but I am very sure
that you will rediscover the information in the preceding paragraph
the hard way.
Bets wishes
Detlev
--
You get 3 opportunities to advertise your Rock band, no more.
-- Proposed Symbolics guidelines for mail messages (1984)
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de
next prev parent reply other threads:[~2007-08-09 13:47 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
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 [this message]
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=m2ps1wyg4f.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).