Searched refs:reply_lock (Results 1 – 2 of 2) sorted by relevance
120 kmutex_t reply_lock; member185 mutex_enter(&xs_state.reply_lock); in read_reply()191 &xs_state.reply_lock) == 0) { in read_reply()192 mutex_exit(&xs_state.reply_lock); in read_reply()197 mutex_exit(&xs_state.reply_lock); in read_reply()200 mutex_enter(&xs_state.reply_lock); in read_reply()211 mutex_exit(&xs_state.reply_lock); in read_reply()1019 mutex_enter(&xs_state.reply_lock); in process_msg()1021 mutex_exit(&xs_state.reply_lock); in process_msg()1079 mutex_init(&xs_state.reply_lock, NULL, MUTEX_DEFAULT, NULL); in xs_early_init()
135 kmutex_t reply_lock; /* mutex for getting reply */ member2838 mutex_enter(&entry->reply_lock); in schpc_reply_handler()2861 mutex_exit(&entry->reply_lock); in schpc_reply_handler()2925 mutex_enter(&listp->reply_lock); in schpc_getreply()2931 rc = cv_timedwait(&listp->reply_cv, &listp->reply_lock, in schpc_getreply()2942 mutex_exit(&listp->reply_lock); in schpc_getreply()2958 mutex_exit(&listp->reply_lock); in schpc_getreply()3033 mutex_init(&entry->reply_lock, NULL, MUTEX_DRIVER, NULL); in schpc_replylist_link()