From: Arjan van de Ven <arjanv@redhat.com>
To: Amol Lad <dal_loma@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wake_up from interrupt handler
Date: 07 Oct 2002 17:36:37 +0200 [thread overview]
Message-ID: <1034004998.2815.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20021007142520.56164.qmail@web12406.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
On Mon, 2002-10-07 at 16:25, Amol Lad wrote:
> In this code too.. lost-wakeup problem is not solved
>
> if (event_occured)
> else
> schedule();
>
> what if in check ' if(event_occured) ' goes to 'else'
> and before calling schedule() my ISR interrupted this
> thread and set the event..
that's fine; the wake_up() will mark your process as TASK_RUNNING at
which point the schedule() is effectively a NOP, at which point your
event loop just loops immediatly again -> no problem
always keep interrupts enabled during this, no need to block them ;)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-07 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 12:41 wake_up from interrupt handler Amol Lad
2002-10-07 13:04 ` Arjan van de Ven
2002-10-07 14:25 ` Amol Lad
2002-10-07 15:36 ` Arjan van de Ven [this message]
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=1034004998.2815.11.camel@localhost.localdomain \
--to=arjanv@redhat.com \
--cc=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.