Lines Matching refs:pseudo
47 pseudo-locking is a unique way of using cache control to "pin" or
118 Corresponding region is pseudo-locked. No
212 When the resource group is in pseudo-locked mode this file will
214 pseudo-locked region.
236 cache pseudo-locked region is created by first writing
237 "pseudo-locksetup" to the "mode" file before writing the cache
238 pseudo-locked region's schemata to the resource group's "schemata"
239 file. On successful pseudo-locked region creation the mode will
240 automatically change to "pseudo-locked".
471 application can fill. Cache pseudo-locking builds on the fact that a
473 allocated area on a cache hit. With cache pseudo-locking, data can be
476 pseudo-locked memory is made accessible to user space where an
480 The creation of a cache pseudo-locked region is triggered by a request
482 to be pseudo-locked. The cache pseudo-locked region is created as follows:
485 from the user of the cache region that will contain the pseudo-locked
488 while the pseudo-locked region exists.
496 pseudo-locked region is protected as long as its CBM does not appear in
497 any CAT allocation. Even though the cache pseudo-locked region will from
499 any CLOS will be able to access the memory in the pseudo-locked region since
504 Cache pseudo-locking increases the probability that data will remain
510 pseudo-locked region creation.
512 It is required that an application using a pseudo-locked region runs
514 with the cache on which the pseudo-locked region resides. A sanity check
515 within the code will not allow an application to map pseudo-locked memory
517 pseudo-locked region resides. The sanity check is only done during the
524 of cache that should be dedicated to pseudo-locking. At this time an
528 pseudo-locked memory into its address space.
532 A pseudo-locked region is created using the resctrl interface as follows:
535 2) Change the new resource group's mode to "pseudo-locksetup" by writing
536 "pseudo-locksetup" to the "mode" file.
537 3) Write the schemata of the pseudo-locked region to the "schemata" file. All
541 On successful pseudo-locked region creation the "mode" file will contain
542 "pseudo-locked" and a new character device with the same name as the resource
544 by user space in order to obtain access to the pseudo-locked memory region.
546 An example of cache pseudo-locked region creation and usage can be found below.
550 The pseudo-locking debugging interface is enabled by default (if
554 location is present in the cache. The pseudo-locking debugging interface uses
556 the pseudo-locked region:
560 example below). In this test the pseudo-locked region is traversed at
568 When a pseudo-locked region is created a new debugfs directory is created for
571 measurement of the pseudo-locked region depends on the number written to this
592 In this example a pseudo-locked region named "newlock" was created. Here is
626 In this example a pseudo-locked region named "newlock" was created on the L2
860 Ensure that there are bits available that can be pseudo-locked, since only
861 unused bits can be pseudo-locked the bits to be pseudo-locked needs to be
870 Create a new resource group that will be associated with the pseudo-locked
871 region, indicate that it will be used for a pseudo-locked region, and
872 configure the requested pseudo-locked region capacity bitmask::
875 # echo pseudo-locksetup > newlock/mode
878 On success the resource group's mode will change to pseudo-locked, the
879 bit_usage will reflect the pseudo-locked region, and the character device
880 exposing the pseudo-locked region will exist::
883 pseudo-locked
892 * Example code to access one page of pseudo-locked cache region
905 * cores associated with the pseudo-locked region. Here the cpu
942 /* Application interacts with pseudo-locked memory @mapping */