Lines Matching full:locked

125 			      Corresponding region is pseudo-locked. No
315 	When the resource group is in pseudo-locked mode this file will
317 	pseudo-locked region.
339 	cache pseudo-locked region is created by first writing
341 	pseudo-locked region's schemata to the resource group's "schemata"
342 	file. On successful pseudo-locked region creation the mode will
343 	automatically change to "pseudo-locked".
640 pseudo-locked memory is made accessible to user space where an
644 The creation of a cache pseudo-locked region is triggered by a request
646 to be pseudo-locked. The cache pseudo-locked region is created as follows:
649   from the user of the cache region that will contain the pseudo-locked
652   while the pseudo-locked region exists.
660   pseudo-locked region is protected as long as its CBM does not appear in
661   any CAT allocation. Even though the cache pseudo-locked region will from
663   any CLOS will be able to access the memory in the pseudo-locked region since
672 “locked” data from cache. Power management C-states may shrink or
674 pseudo-locked region creation.
676 It is required that an application using a pseudo-locked region runs
678 with the cache on which the pseudo-locked region resides. A sanity check
679 within the code will not allow an application to map pseudo-locked memory
681 pseudo-locked region resides. The sanity check is only done during the
692    pseudo-locked memory into its address space.
696 A pseudo-locked region is created using the resctrl interface as follows:
701 3) Write the schemata of the pseudo-locked region to the "schemata" file. All
705 On successful pseudo-locked region creation the "mode" file will contain
706 "pseudo-locked" and a new character device with the same name as the resource
708 by user space in order to obtain access to the pseudo-locked memory region.
710 An example of cache pseudo-locked region creation and usage can be found below.
720 the pseudo-locked region:
724    example below). In this test the pseudo-locked region is traversed at
732 When a pseudo-locked region is created a new debugfs directory is created for
735 measurement of the pseudo-locked region depends on the number written to this
756 In this example a pseudo-locked region named "newlock" was created. Here is
790 In this example a pseudo-locked region named "newlock" was created on the L2
1016 Lock portion of L2 cache from cache id 1 using CBM 0x3. Pseudo-locked
1024 Ensure that there are bits available that can be pseudo-locked, since only
1025 unused bits can be pseudo-locked the bits to be pseudo-locked needs to be
1034 Create a new resource group that will be associated with the pseudo-locked
1035 region, indicate that it will be used for a pseudo-locked region, and
1036 configure the requested pseudo-locked region capacity bitmask::
1042 On success the resource group's mode will change to pseudo-locked, the
1043 bit_usage will reflect the pseudo-locked region, and the character device
1044 exposing the pseudo-locked region will exist::
1047   pseudo-locked
1056   * Example code to access one page of pseudo-locked cache region
1069   * cores associated with the pseudo-locked region. Here the cpu
1106     /* Application interacts with pseudo-locked memory @mapping */