Lines Matching full:locked

142 			      Corresponding region is pseudo-locked. No
572 	When the resource group is in pseudo-locked mode this file will
574 	pseudo-locked region.
596 	cache pseudo-locked region is created by first writing
598 	pseudo-locked region's schemata to the resource group's "schemata"
599 	file. On successful pseudo-locked region creation the mode will
600 	automatically change to "pseudo-locked".
1041 pseudo-locked memory is made accessible to user space where an
1045 The creation of a cache pseudo-locked region is triggered by a request
1047 to be pseudo-locked. The cache pseudo-locked region is created as follows:
1050   from the user of the cache region that will contain the pseudo-locked
1053   while the pseudo-locked region exists.
1061   pseudo-locked region is protected as long as its CBM does not appear in
1062   any CAT allocation. Even though the cache pseudo-locked region will from
1064   any CLOS will be able to access the memory in the pseudo-locked region since
1073 “locked” data from cache. Power management C-states may shrink or
1075 pseudo-locked region creation.
1077 It is required that an application using a pseudo-locked region runs
1079 with the cache on which the pseudo-locked region resides. A sanity check
1080 within the code will not allow an application to map pseudo-locked memory
1082 pseudo-locked region resides. The sanity check is only done during the
1093    pseudo-locked memory into its address space.
1097 A pseudo-locked region is created using the resctrl interface as follows:
1102 3) Write the schemata of the pseudo-locked region to the "schemata" file. All
1106 On successful pseudo-locked region creation the "mode" file will contain
1107 "pseudo-locked" and a new character device with the same name as the resource
1109 by user space in order to obtain access to the pseudo-locked memory region.
1111 An example of cache pseudo-locked region creation and usage can be found below.
1121 the pseudo-locked region:
1125    example below). In this test the pseudo-locked region is traversed at
1133 When a pseudo-locked region is created a new debugfs directory is created for
1136 measurement of the pseudo-locked region depends on the number written to this
1157 In this example a pseudo-locked region named "newlock" was created. Here is
1191 In this example a pseudo-locked region named "newlock" was created on the L2
1417 Lock portion of L2 cache from cache id 1 using CBM 0x3. Pseudo-locked
1425 Ensure that there are bits available that can be pseudo-locked, since only
1426 unused bits can be pseudo-locked the bits to be pseudo-locked needs to be
1435 Create a new resource group that will be associated with the pseudo-locked
1436 region, indicate that it will be used for a pseudo-locked region, and
1437 configure the requested pseudo-locked region capacity bitmask::
1443 On success the resource group's mode will change to pseudo-locked, the
1444 bit_usage will reflect the pseudo-locked region, and the character device
1445 exposing the pseudo-locked region will exist::
1448   pseudo-locked
1457   * Example code to access one page of pseudo-locked cache region
1470   * cores associated with the pseudo-locked region. Here the cpu
1507     /* Application interacts with pseudo-locked memory @mapping */