site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On 7 Sep 2007, at 23:29, Régis Duchesne wrote: Jonas wrote: You could have a look at to which kernel api sched_yield() is connected. Good idea. Indeed, sched_yield() calls the swtch_pri() system call with zero as only argument (the argument is not used by swtch_pri() so it does not matter anyway). That in turn is connected to thread_block_reason() which you cannot call form a kext but that is called from thread_block () which I suggested to you in my previous email so my answer of using thread_block(THREAD_CONTINUE_NULL) may well turn out to be a winner here! This email sent to site_archiver@lists.apple.com