Lines Matching full:locking

5  * Pseudo-locking support built on top of Cache Allocation Technology (CAT)
214  * required for pseudo-locking is deduced from this data and &struct
219  * - a cpu associated with the cache instance on which the pseudo-locking
359  * A resource group used for cache pseudo-locking cannot have cpus or tasks
484 	 * Cache Pseudo-locking not supported when CDP is enabled.  in rdtgroup_locksetup_enter()
490 	 *   The implication for pseudo-locking is that if a  in rdtgroup_locksetup_enter()
498 	 *   expose one of the CDP resources to pseudo-locking and  in rdtgroup_locksetup_enter()
502 	 * - If only one region is exposed to pseudo-locking we should  in rdtgroup_locksetup_enter()
504 	 *   for pseudo-locking should take into account both resources.  in rdtgroup_locksetup_enter()
517 	 * platform does not support Cache Pseudo-Locking.  in rdtgroup_locksetup_enter()
520 		rdt_last_cmd_puts("Pseudo-locking not supported\n");  in rdtgroup_locksetup_enter()
553 	 * anymore when this group would be used for pseudo-locking. This  in rdtgroup_locksetup_enter()
791  * information and ready for the user to re-attempt pseudo-locking by
827 		rdt_last_cmd_printf("Locking thread returned error %d\n", ret);  in rdtgroup_pseudo_lock_create()
840 		 * empty pseudo-locking loop.  in rdtgroup_pseudo_lock_create()
842 		rdt_last_cmd_puts("Locking thread interrupted\n");  in rdtgroup_pseudo_lock_create()