Lines Matching full:locked

118 			      Corresponding region is pseudo-locked. No
224 	When the resource group is in pseudo-locked mode this file will
226 	pseudo-locked region.
248 	cache pseudo-locked region is created by first writing
250 	pseudo-locked region's schemata to the resource group's "schemata"
251 	file. On successful pseudo-locked region creation the mode will
252 	automatically change to "pseudo-locked".
490 pseudo-locked memory is made accessible to user space where an
494 The creation of a cache pseudo-locked region is triggered by a request
496 to be pseudo-locked. The cache pseudo-locked region is created as follows:
499   from the user of the cache region that will contain the pseudo-locked
502   while the pseudo-locked region exists.
510   pseudo-locked region is protected as long as its CBM does not appear in
511   any CAT allocation. Even though the cache pseudo-locked region will from
513   any CLOS will be able to access the memory in the pseudo-locked region since
522 “locked” data from cache. Power management C-states may shrink or
524 pseudo-locked region creation.
526 It is required that an application using a pseudo-locked region runs
528 with the cache on which the pseudo-locked region resides. A sanity check
529 within the code will not allow an application to map pseudo-locked memory
531 pseudo-locked region resides. The sanity check is only done during the
542    pseudo-locked memory into its address space.
546 A pseudo-locked region is created using the resctrl interface as follows:
551 3) Write the schemata of the pseudo-locked region to the "schemata" file. All
555 On successful pseudo-locked region creation the "mode" file will contain
556 "pseudo-locked" and a new character device with the same name as the resource
558 by user space in order to obtain access to the pseudo-locked memory region.
560 An example of cache pseudo-locked region creation and usage can be found below.
570 the pseudo-locked region:
574    example below). In this test the pseudo-locked region is traversed at
582 When a pseudo-locked region is created a new debugfs directory is created for
585 measurement of the pseudo-locked region depends on the number written to this
606 In this example a pseudo-locked region named "newlock" was created. Here is
640 In this example a pseudo-locked region named "newlock" was created on the L2
866 Lock portion of L2 cache from cache id 1 using CBM 0x3. Pseudo-locked
874 Ensure that there are bits available that can be pseudo-locked, since only
875 unused bits can be pseudo-locked the bits to be pseudo-locked needs to be
884 Create a new resource group that will be associated with the pseudo-locked
885 region, indicate that it will be used for a pseudo-locked region, and
886 configure the requested pseudo-locked region capacity bitmask::
892 On success the resource group's mode will change to pseudo-locked, the
893 bit_usage will reflect the pseudo-locked region, and the character device
894 exposing the pseudo-locked region will exist::
897   pseudo-locked
906   * Example code to access one page of pseudo-locked cache region
919   * cores associated with the pseudo-locked region. Here the cpu
956     /* Application interacts with pseudo-locked memory @mapping */