Lines Matching defs:remote

332  * Required event and timerqueue update after a remote expiry:
335  * After expiring timers of a remote CPU, a walk through the hierarchy and
338  * remote CPU is still idle.
361  * 2. CPU2 starts to expire remote timers. It starts with LVL0 group
525  *			be back in time. When using this value in the remote
527  *			struct of CPU which expires remote timers. It is updated
538  * @remote:		Is set, when the new timer path is executed in
542  * @check:		is set if there is the need to handle remote timers;
550 	bool			remote;
764 	bool remote = data->remote;
787 		 * If the current writer wins, a useless remote expiration may
801 		 * remote expiry was done before. This ensures to not lose
803 		 * "Required event and timerqueue update after a remote
806 		 * The two call sites which are executed without a remote expiry
823 		if (ignore && !remote && group->parent)
850 		 * KTIME_MAX) and there was no remote timer handling before or
855 		 * if a remote timer handling was executed before and the group
861 		if (!remote || groupstate.active)
876 		 * Nothing to do when update was done during remote timer
881 		if (remote)
926 	if (tmc->remote)
932 	data.remote = false;
952 	 * If the remote CPU is offline then the timers have been migrated to
955 	 * If tmigr_cpu::remote is set, at the moment another CPU already
956 	 * expires the timers of the remote CPU.
966 	if (!tmc->available || tmc->remote || tmc->cpuevt.ignore ||
974 	tmc->remote = true;
977 	/* Drop the lock to allow the remote CPU to exit idle */
996 	 * whether the remote CPU went offline in the meantime and after
997 	 * fetching the next remote timer interrupt. Dropping the locks as fast
1015 	 * remote expiry" in the documentation at the top)
1029 	data.remote = true;
1033 	 * on the remote CPU (see section "Required event and timerqueue update
1034 	 * after a remote expiry" in the documentation at the top)
1039 	tmc->remote = false;
1095  * tmigr_handle_remote() - Handle global timers of remote idle CPUs
1129 	 * KTIME_MAX. Even if tmc->lock is not held during the whole remote
1184  * tmigr_requires_handle_remote() - Check the need of remote timer handling
1204 	 * If the CPU is active, walk the hierarchy to check whether a remote
1344 	data->remote = false;
2066 				 * No other available CPUs in the remote hierarchy. Link the
2095 	tmc->remote = false;