Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)

• Subject: Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)
• From: Andrew Gallatin <email@hidden>
• Date: Fri, 20 May 2005 21:45:24 -0400 (EDT)
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Godfrey van der Linden writes:
 > The good news is that assert_wait/thread_block are a formal part of  
 > the Mach kpi set so they are expected to work consistently and  
 > without RRBC issues going forward.

Excellent.  And I assume that assert_wait_timeout() is included in
that formal KPI?

 > I think in this case you may be better off rolling your own.  I  
 > suggest however that you don't use the  
 > IOSimpleLockLockWithDisableInterrupt but rather iofies->disable()

Actually, I'm going to have to use a lock because wakeups can also
(rarely) come from a thread context.  But you had no way to know
that...

Thanks for the info!

Drew
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-drivers/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)
    • From: Godfrey van der Linden <email@hidden>

• Prev by Date: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)
• Next by Date: NetworkAudioDevice compilation problems
• Previous by thread: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)
• Next by thread: Re: IOFIES Filter wakeup (was: why no IOSimpleLockSleep()?)
• Index(es):
  • Date
  • Thread