From: "Madhu Saravana Sibi Govindan" <ssshayagriva@gmail.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Using "Asynchronous Notifications" within an interrupt handler
Date: Fri, 6 Oct 2006 12:10:09 -0500 [thread overview]
Message-ID: <513a5e60610061010k2fb0b8cex245f009d8d79de69@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0610060741040.12702@yvahk01.tjqt.qr>
Thanks for the information.
I have another quick question: my device driver can expect up to 4
different interrupts (from 4 hardware devices). Can I send a posix
real-time signal (SIGRTMIN) using the kill_async interface and expect
the kernel to queue these signals for delievery to the sleeping
process? (Because if I use SIGIO it is possible that an incoming
interrupt is lost because the kernel doesn't queue up normal signals,
right?).
Thanks,
G.Sibi
On 10/6/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> >
> > My question is: is it safe to use the asynchronous notification
> > mechanism within an interrupt handler? I see that this call acquires a
> > bunch of locks before sending the signal to the process. Would this
> > cause any deadlocking situations? Or should I resort to the top and
> > bottom half approach for interrupt handling and handle the
> > notification in the bottom half?
>
> It may be possible - I have an old driver for custom hardware lying
> around here, and it does this in the irq handler:
>
> kill_fasync(&global.fasync_ptr, SIGIO, POLL_IN);
>
>
>
> -`J'
> --
>
prev parent reply other threads:[~2006-10-06 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <513a5e60610051727t7f7c7b78u62410c4b8f8502a7@mail.gmail.com>
2006-10-06 0:53 ` Madhu Saravana Sibi Govindan
2006-10-06 5:42 ` Jan Engelhardt
2006-10-06 17:10 ` Madhu Saravana Sibi Govindan [this message]
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=513a5e60610061010k2fb0b8cex245f009d8d79de69@mail.gmail.com \
--to=ssshayagriva@gmail.com \
--cc=jengelh@linux01.gwdg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®