From: Amol Lad <dal_loma@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: wake_up from interrupt handler
Date: Mon, 7 Oct 2002 05:41:21 -0700 (PDT) [thread overview]
Message-ID: <20021007124121.37417.qmail@web12407.mail.yahoo.com> (raw)
Hi,
I have a kernel thread which did add_to_wait_queue()
to wait for an event.
The event for which above thread is waiting occurs in
an interrupt handler that calls wake_up() to wake the
above thread.
Now I am faced with a 'lost wakeup' problem, in which
the
kernel thread checks whether event occured, he finds
it to be 'not-occured' but before calling
add_to_wait_queue(), interrupt handler detects that
the event has occured and calls wake_up().
My thread sleeps forever.
I know some new APIs are provided in recent 2.5
kernel, but how to avoid this in 2.4.18
please CC me
Thanks
Amol
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
next reply other threads:[~2002-10-07 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 12:41 Amol Lad [this message]
2002-10-07 13:04 ` wake_up from interrupt handler Arjan van de Ven
2002-10-07 14:25 ` Amol Lad
2002-10-07 15:36 ` Arjan van de Ven
2002-10-07 17:44 ` Mike Galbraith
2002-10-07 22:52 ` Rui Sousa
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=20021007124121.37417.qmail@web12407.mail.yahoo.com \
--to=dal_loma@yahoo.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 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.