Searched refs:awaken (Results 1 – 13 of 13) sorted by relevance
427 int ret, awaken; in __key_instantiate_and_link() local432 awaken = 0; in __key_instantiate_and_link()448 awaken = 1; in __key_instantiate_and_link()472 if (awaken) in __key_instantiate_and_link()576 int ret, awaken, link_ret = 0; in key_reject_and_link() local581 awaken = 0; in key_reject_and_link()607 awaken = 1; in key_reject_and_link()626 if (awaken) in key_reject_and_link()
714 bool awaken = false; in __fscache_disable_cookie() local754 awaken = true; in __fscache_disable_cookie()757 if (awaken) in __fscache_disable_cookie()
705 bool awaken = false; in fscache_drop_object() local724 awaken = true; in fscache_drop_object()727 if (awaken) in fscache_drop_object()
162 bool awaken:1; member
112 evo_data(push, asyw->ntfy.awaken << 30 | asyw->ntfy.offset); in ovly507e_ntfy_set()
142 evo_data(push, asyw->ntfy.awaken << 30 | asyw->ntfy.offset); in base507c_ntfy_set()
168 evo_data(push, asyw->ntfy.offset | asyw->ntfy.awaken); in wndwc37e_ntfy_set()
173 asyw->ntfy.awaken = false; in nv50_wndw_ntfy_enable()
44 (only to be awaken quite soon)
3805 awaken the corresponding "rcuoN" kthreads,
152 to be awaken for these requests. Sleeping VCPUs will handle the153 requests when they are awaken later for some other reason.284 to check if it should awaken. One reason to do so is to provide
188 allocation request will awaken the ``kswapd`` daemon. It will
191 a timer will awaken these CPUs every four jiffies in order to ensure
