5  * Pseudo-locking support built on top of Cache Allocation Technology (CAT)
29  * pseudo-locked regions.
85  * region_find_by_minor - Locate a pseudo-lock region by inode minor number
86  * @minor: The minor number of the device representing pseudo-locked region
89  * pseudo-locked region it belongs to. This is done by matching the minor
90  * number of the device to the pseudo-locked region it belongs.
92  * Minor numbers are assigned at the time a pseudo-locked region is associated
95  * Return: On success return pointer to resource group owning the pseudo-locked
113  * @list:	Entry within the @pm_reqs list for a pseudo-locked region
134  * @plr: Pseudo-locked region
185  * pseudo_lock_region_clear - Reset pseudo-lock region data
186  * @plr: pseudo-lock region
188  * All content of the pseudo-locked region is reset - any memory allocated
208  * pseudo_lock_region_init - Initialize pseudo-lock region information
209  * @plr: pseudo-lock region
211  * Called after user provided a schemata to be pseudo-locked. From the
214  * required for pseudo-locking is deduced from this data and &struct
216  * - size in bytes of the region to be pseudo-locked
218  *   to be pseudo-locked
219  * - a cpu associated with the cache instance on which the pseudo-locking
259  * pseudo_lock_init - Initialize a pseudo-lock region
260  * @rdtgrp: resource group to which new pseudo-locked region will belong
262  * A pseudo-locked region is associated with a resource group. When this
263  * association is created the pseudo-locked region is initialized. The
264  * details of the pseudo-locked region are not known at this time so only
284  * pseudo_lock_region_alloc - Allocate kernel memory that will be pseudo-locked
285  * @plr: pseudo-lock region
287  * Initialize the details required to set up the pseudo-locked region and
288  * allocate the contiguous memory that will be pseudo-locked to the cache.
327  * pseudo_lock_free - Free a pseudo-locked region
328  * @rdtgrp: resource group to which pseudo-locked region belonged
330  * The pseudo-locked region's resources have already been released, or not
359  * A resource group used for cache pseudo-locking cannot have cpus or tasks
457  * to represent a pseudo-locked region and is in the process of being set
458  * up to do so. A resource group used for a pseudo-locked region would
461  * future. Monitoring of a pseudo-locked region is not allowed either.
463  * The above and more restrictions on a pseudo-locked region are checked
479 		rdt_last_cmd_puts("Cannot pseudo-lock default group\n");  in rdtgroup_locksetup_enter()
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()
491 	 *   pseudo-locked region is created on a domain of one  in rdtgroup_locksetup_enter()
492 	 *   resource (eg. L3CODE), then a pseudo-locked region cannot  in rdtgroup_locksetup_enter()
495 	 *   pseudo-locked region involves a call to wbinvd that will  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()
505 	 *   Similarly, if a pseudo-locked region is created in one  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()
546 		rdt_last_cmd_puts("Unable to init pseudo-lock region\n");  in rdtgroup_locksetup_enter()
553 	 * anymore when this group would be used for pseudo-locking. This  in rdtgroup_locksetup_enter()
600  * rdtgroup_cbm_overlaps_pseudo_locked - Test if CBM or portion is pseudo-locked
606  * pseudo-locked region on @d.
611  * Return: true if @cbm overlaps with pseudo-locked region on @d, false
629  * rdtgroup_pseudo_locked_in_hierarchy - Pseudo-locked region in cache hierarchy
632  * The setup of a pseudo-locked region affects all cache instances within
634  * pseudo-locked regions exist within a cache hierarchy to prevent any
635  * attempts to create new pseudo-locked regions in the same hierarchy.
637  * Return: true if a pseudo-locked region exists in the hierarchy of @d or
655 	 * First determine which cpus have pseudo-locked regions  in rdtgroup_pseudo_locked_in_hierarchy()
667 	 * Next test if new pseudo-locked region would intersect with  in rdtgroup_pseudo_locked_in_hierarchy()
678  * pseudo_lock_measure_cycles - Trigger latency measure to pseudo-locked region
679  * @rdtgrp: Resource group to which the pseudo-locked region belongs.
680  * @sel: Selector of which measurement to perform on a pseudo-locked region.
682  * The measurement of latency to access a pseudo-locked region should be
683  * done from a cpu that is associated with that pseudo-locked region.
782  * rdtgroup_pseudo_lock_create - Create a pseudo-locked region
783  * @rdtgrp: resource group to which pseudo-lock region belongs
785  * Called when a resource group in the pseudo-locksetup mode receives a
786  * valid schemata that should be pseudo-locked. Since the resource group is
787  * in pseudo-locksetup mode the &struct pseudo_lock_region has already been
789  * occurs the resource group remains in the pseudo-locksetup mode with the
791  * information and ready for the user to re-attempt pseudo-locking by
794  * Return: 0 if the pseudo-locked region was successfully pseudo-locked, <0
840 		 * empty pseudo-locking loop.  in rdtgroup_pseudo_lock_create()
854 	 * pseudo-locked region will still be here on return.  in rdtgroup_pseudo_lock_create()
914  * rdtgroup_pseudo_lock_remove - Remove a pseudo-locked region
915  * @rdtgrp: resource group to which the pseudo-locked region belongs
917  * The removal of a pseudo-locked region can be initiated when the resource
920  * not go back to pseudo-locksetup mode before it is removed, instead it is
933 		 * Default group cannot be a pseudo-locked region so we can  in rdtgroup_pseudo_lock_remove()
1026 	 * with the pseudo-locked region. If this is not the case the task  in pseudo_lock_dev_mmap_prepare()
1028 	 * pseudo-locked region.  in pseudo_lock_dev_mmap_prepare()