43  * pseudo-locked regions.
70  * pseudo-locking. This includes testing to ensure pseudo-locked regions
72  * as well as that these pseudo-locked regions can maintain their low cache
159  * @minor: The minor number of the device representing pseudo-locked region
162  * pseudo-locked region it belongs to. This is done by matching the minor
163  * number of the device to the pseudo-locked region it belongs.
165  * Minor numbers are assigned at the time a pseudo-locked region is associated
168  * Return: On success return pointer to resource group owning the pseudo-locked
186  * @list:	Entry within the @pm_reqs list for a pseudo-locked region
207  * @plr: Pseudo-locked region
261  * All content of the pseudo-locked region is reset - any memory allocated
284  * Called after user provided a schemata to be pseudo-locked. From the
289  * - size in bytes of the region to be pseudo-locked
291  *   to be pseudo-locked
333  * @rdtgrp: resource group to which new pseudo-locked region will belong
335  * A pseudo-locked region is associated with a resource group. When this
336  * association is created the pseudo-locked region is initialized. The
337  * details of the pseudo-locked region are not known at this time so only
357  * pseudo_lock_region_alloc - Allocate kernel memory that will be pseudo-locked
360  * Initialize the details required to set up the pseudo-locked region and
361  * allocate the contiguous memory that will be pseudo-locked to the cache.
400  * pseudo_lock_free - Free a pseudo-locked region
401  * @rdtgrp: resource group to which pseudo-locked region belonged
403  * The pseudo-locked region's resources have already been released, or not
425  * with class of service set to the bitmask of the pseudo-locked region.
430  * to be locked is the only memory access made during the critical locking
461 	 * will get a cache hit in below loop from outside of pseudo-locked  in resctrl_arch_pseudo_lock_fn()
480 	 * being pseudo-locked is reached the hardware will not read beyond  in resctrl_arch_pseudo_lock_fn()
481 	 * the buffer and evict pseudo-locked memory read earlier from the  in resctrl_arch_pseudo_lock_fn()
494 	 * pseudo-locked followed by reading of kernel memory to load it  in resctrl_arch_pseudo_lock_fn()
532 	 * does not overlap with pseudo-locked region.  in resctrl_arch_pseudo_lock_fn()
659  * to represent a pseudo-locked region and is in the process of being set
660  * up to do so. A resource group used for a pseudo-locked region would
663  * future. Monitoring of a pseudo-locked region is not allowed either.
665  * The above and more restrictions on a pseudo-locked region are checked
693 	 *   pseudo-locked region is created on a domain of one  in rdtgroup_locksetup_enter()
694 	 *   resource (eg. L3CODE), then a pseudo-locked region cannot  in rdtgroup_locksetup_enter()
697 	 *   pseudo-locked region involves a call to wbinvd that will  in rdtgroup_locksetup_enter()
707 	 *   Similarly, if a pseudo-locked region is created in one  in rdtgroup_locksetup_enter()
802  * rdtgroup_cbm_overlaps_pseudo_locked - Test if CBM or portion is pseudo-locked
808  * pseudo-locked region on @d.
813  * Return: true if @cbm overlaps with pseudo-locked region on @d, false
831  * rdtgroup_pseudo_locked_in_hierarchy - Pseudo-locked region in cache hierarchy
834  * The setup of a pseudo-locked region affects all cache instances within
836  * pseudo-locked regions exist within a cache hierarchy to prevent any
837  * attempts to create new pseudo-locked regions in the same hierarchy.
839  * Return: true if a pseudo-locked region exists in the hierarchy of @d or
857 	 * First determine which cpus have pseudo-locked regions  in rdtgroup_pseudo_locked_in_hierarchy()
869 	 * Next test if new pseudo-locked region would intersect with  in rdtgroup_pseudo_locked_in_hierarchy()
881  *                                      pseudo-locked memory
1173  * pseudo_lock_measure_cycles - Trigger latency measure to pseudo-locked region
1174  * @rdtgrp: Resource group to which the pseudo-locked region belongs.
1175  * @sel: Selector of which measurement to perform on a pseudo-locked region.
1177  * The measurement of latency to access a pseudo-locked region should be
1178  * done from a cpu that is associated with that pseudo-locked region.
1281  * rdtgroup_pseudo_lock_create - Create a pseudo-locked region
1285  * valid schemata that should be pseudo-locked. Since the resource group is
1293  * Return: 0 if the pseudo-locked region was successfully pseudo-locked, <0
1353 	 * pseudo-locked region will still be here on return.  in rdtgroup_pseudo_lock_create()
1413  * rdtgroup_pseudo_lock_remove - Remove a pseudo-locked region
1414  * @rdtgrp: resource group to which the pseudo-locked region belongs
1416  * The removal of a pseudo-locked region can be initiated when the resource
1432 		 * Default group cannot be a pseudo-locked region so we can  in rdtgroup_pseudo_lock_remove()
1524 	 * with the pseudo-locked region. If this is not the case the task  in pseudo_lock_dev_mmap()
1526 	 * pseudo-locked region.  in pseudo_lock_dev_mmap()