site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Feb 11, 2008, at 3:42 PM, mm w wrote: hi Greg, yep these mechanisms exist, this is the first things that you implement when you write a lock system no matter on what: islockable and islocked try to understand, what you do (if you use a lck object (locked)) if your lock object has been created, a lock has been aquired when you create a lock object, the lock system test it for you Thanks! - Greg Thanks! - Greg _______________________________________________ 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... -mmw Hi mmw, thanks for your reply. I was specifically wondering how I could do this from a kernel extension? I don't see a header in Kernel.framework that contains any try_lock functions for lck_mtx_t. Hmm... I've found this in the sources to xnu, but I can't find this in the Kernel.framework. Perhaps I should have mentioned that I'm writing a kernel extension. Does this exist for kernel extensions, and if so how do I access it? Right now I'm just linking against Kernel.framework, which doesn't seem to have this header. This email sent to site_archiver@lists.apple.com