From: "Madhu Saravana Sibi Govindan" <ssshayagriva@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Using "Asynchronous Notifications" within an interrupt handler
Date: Thu, 5 Oct 2006 19:53:02 -0500 [thread overview]
Message-ID: <513a5e60610051753o1dd828c4i52b8ba563601694a@mail.gmail.com> (raw)
In-Reply-To: <513a5e60610051727t7f7c7b78u62410c4b8f8502a7@mail.gmail.com>
Hello all,
I'm developing a linux device driver for kernel version 2.16.15. I'm
thinking of using the "Asynchronous Notification" mechanism, explained
in the Linux Device Drivers book by Corbet and Rubini in Chapter 6,
within an interrupt handler.
The idea is: whenever the device driver receives an interrupt from the
hardware device, the interrupt handler uses this 'asynchronous
notification' mechanism to notify a user-level process of this
interrupt. The user-level process, on the other hand, is waiting for
this SIGIO signal from the device driver.
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?
I'd be very thankful for suggestions/ideas on this topic.
Regards and thanks in advance,
G.Sibi
PS: I've posted this to os_drivers@lists.osdl.org too. My apologies
for the duplication.
next parent reply other threads:[~2006-10-06 0:53 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 [this message]
2006-10-06 5:42 ` Jan Engelhardt
2006-10-06 17:10 ` Madhu Saravana Sibi Govindan
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=513a5e60610051753o1dd828c4i52b8ba563601694a@mail.gmail.com \
--to=ssshayagriva@gmail.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
all inboxes | Powered by JetHome®