44  * pseudo-locked regions.
55  * pseudo-locking. This includes testing to ensure pseudo-locked regions
57  * as well as that these pseudo-locked regions can maintain their low cache
140  * @minor: The minor number of the device representing pseudo-locked region
143  * pseudo-locked region it belongs to. This is done by matching the minor
144  * number of the device to the pseudo-locked region it belongs.
146  * Minor numbers are assigned at the time a pseudo-locked region is associated
149  * Return: On success return pointer to resource group owning the pseudo-locked
167  * @list:	Entry within the @pm_reqs list for a pseudo-locked region
188  * @plr: Pseudo-locked region
242  * All content of the pseudo-locked region is reset - any memory allocated
265  * Called after user provided a schemata to be pseudo-locked. From the
270  * - size in bytes of the region to be pseudo-locked
272  *   to be pseudo-locked
315  * @rdtgrp: resource group to which new pseudo-locked region will belong
317  * A pseudo-locked region is associated with a resource group. When this
318  * association is created the pseudo-locked region is initialized. The
319  * details of the pseudo-locked region are not known at this time so only
339  * pseudo_lock_region_alloc - Allocate kernel memory that will be pseudo-locked
342  * Initialize the details required to set up the pseudo-locked region and
343  * allocate the contiguous memory that will be pseudo-locked to the cache.
382  * pseudo_lock_free - Free a pseudo-locked region
383  * @rdtgrp: resource group to which pseudo-locked region belonged
385  * The pseudo-locked region's resources have already been released, or not
407  * with class of service set to the bitmask of the pseudo-locked region.
412  * to be locked is the only memory access made during the critical locking
444 	 * will get a cache hit in below loop from outside of pseudo-locked  in pseudo_lock_fn()
463 	 * being pseudo-locked is reached the hardware will not read beyond  in pseudo_lock_fn()
464 	 * the buffer and evict pseudo-locked memory read earlier from the  in pseudo_lock_fn()
477 	 * pseudo-locked followed by reading of kernel memory to load it  in pseudo_lock_fn()
514 	 * does not overlap with pseudo-locked region.  in pseudo_lock_fn()
641  * to represent a pseudo-locked region and is in the process of being set
642  * up to do so. A resource group used for a pseudo-locked region would
645  * future. Monitoring of a pseudo-locked region is not allowed either.
647  * The above and more restrictions on a pseudo-locked region are checked
675 	 *   pseudo-locked region is created on a domain of one  in rdtgroup_locksetup_enter()
676 	 *   resource (eg. L3CODE), then a pseudo-locked region cannot  in rdtgroup_locksetup_enter()
679 	 *   pseudo-locked region involves a call to wbinvd that will  in rdtgroup_locksetup_enter()
689 	 *   Similarly, if a pseudo-locked region is created in one  in rdtgroup_locksetup_enter()
785  * rdtgroup_cbm_overlaps_pseudo_locked - Test if CBM or portion is pseudo-locked
791  * pseudo-locked region on @d.
796  * Return: true if @cbm overlaps with pseudo-locked region on @d, false
814  * rdtgroup_pseudo_locked_in_hierarchy - Pseudo-locked region in cache hierarchy
817  * The setup of a pseudo-locked region affects all cache instances within
819  * pseudo-locked regions exist within a cache hierarchy to prevent any
820  * attempts to create new pseudo-locked regions in the same hierarchy.
822  * Return: true if a pseudo-locked region exists in the hierarchy of @d or
837 	 * First determine which cpus have pseudo-locked regions  in rdtgroup_pseudo_locked_in_hierarchy()
849 	 * Next test if new pseudo-locked region would intersect with  in rdtgroup_pseudo_locked_in_hierarchy()
860  * measure_cycles_lat_fn - Measure cycle latency to read pseudo-locked memory
1152  * pseudo_lock_measure_cycles - Trigger latency measure to pseudo-locked region
1153  * @rdtgrp: Resource group to which the pseudo-locked region belongs.
1154  * @sel: Selector of which measurement to perform on a pseudo-locked region.
1156  * The measurement of latency to access a pseudo-locked region should be
1157  * done from a cpu that is associated with that pseudo-locked region.
1268  * rdtgroup_pseudo_lock_create - Create a pseudo-locked region
1272  * valid schemata that should be pseudo-locked. Since the resource group is
1280  * Return: 0 if the pseudo-locked region was successfully pseudo-locked, <0
1338 	 * pseudo-locked region will still be here on return.  in rdtgroup_pseudo_lock_create()
1399  * rdtgroup_pseudo_lock_remove - Remove a pseudo-locked region
1400  * @rdtgrp: resource group to which the pseudo-locked region belongs
1402  * The removal of a pseudo-locked region can be initiated when the resource
1418 		 * Default group cannot be a pseudo-locked region so we can  in rdtgroup_pseudo_lock_remove()
1510 	 * with the pseudo-locked region. If this is not the case the task  in pseudo_lock_dev_mmap()
1512 	 * pseudo-locked region.  in pseudo_lock_dev_mmap()