LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ming Liu" <eemingliu@hotmail.com>
To: domen.puncer@telargo.com
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: basic and stupid question on wait_event and wake_up
Date: Mon, 13 Aug 2007 09:46:17 +0000	[thread overview]
Message-ID: <BAY138-F400F2CE580BD3EB48B9A3CB2DC0@phx.gbl> (raw)
In-Reply-To: <20070813093107.GG13994@moe.telargo.com>

Thank you so much for your explanation. Now I am quite clear on this topic. 


Domen, Sorry for my misspelling of your name. That should be "Domen" not 
"Momen". Sorry for that. :)

BR
Ming


>From: Domen Puncer <domen.puncer@telargo.com>
>To: Ming Liu <eemingliu@hotmail.com>
>CC: Linuxppc-embedded@ozlabs.org
>Subject: Re: basic and stupid question on wait_event and wake_up
>Date: Mon, 13 Aug 2007 11:31:07 +0200
>
>On 13/08/07 09:22 +0000, Ming Liu wrote:
> > Dear Momen,
> > OK. I see now. So you mean condition is only to judge whether a 
sleeping
> > process could be waken up or not when wake_up() is executed in other
> > processes or interrupt handlers. What really wakes the process up is 
still
> > the function of wake_up, right? We just execute wake_up() and then 
check if
> > condition is true. If yes, the process will leave its sleeping and wake 
up;
> > if not, it keep sleeping. Am I right?
>
>Right.
>
>
>	Domen

_________________________________________________________________
免费下载 MSN Explorer:   http://explorer.msn.com/lccn/  

      reply	other threads:[~2007-08-13  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 13:57 basic and stupid question on wait_event and wake_up Ming Liu
2007-08-13  7:54 ` Domen Puncer
2007-08-13  8:33   ` Ming Liu
2007-08-13  8:47     ` Domen Puncer
2007-08-13  9:22       ` Ming Liu
2007-08-13  9:30         ` Laurent Pinchart
2007-08-13  9:31         ` Domen Puncer
2007-08-13  9:46           ` Ming Liu [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=BAY138-F400F2CE580BD3EB48B9A3CB2DC0@phx.gbl \
    --to=eemingliu@hotmail.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=domen.puncer@telargo.com \
    /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