rdt_last_cmd

Type	Parameter	Name
const char *	s

**Caller**
Name	Describe
rdtgroup_cpus_show
cpus_mon_write
cpus_ctrl_write
rdtgroup_cpus_write
__rdtgroup_move_task
rdtgroup_tasks_write
rdtgroup_mode_test_exclusive	dtgroup_mode_test_exclusive - Test if this resource group can be exclusive* An exclusive resource group implies that there should be no sharing of* its allocated resources
rdtgroup_mode_write	dtgroup_mode_write - Modify the resource group's mode
rdtgroup_size_show	dtgroup_size_show - Display size in bytes of allocated regions* The "size" file mirrors the layout of the "schemata" file, printing the* size in bytes of each region instead of the capacity bitmask.
rdtgroup_init_alloc	Initialize the RDT group's allocations.
mkdir_rdt_prepare
rdtgroup_mkdir_ctrl_mon	These are rdtgroups created under the root directory. Can be used* to allocate and monitor resources.
bw_validate	Check whether MBA bandwidth percentage value is correct. The value is* checked against the minimum and max bandwidth values specified by the* hardware. The allocated bandwidth percentage is rounded to the next* control step available on the hardware.
cbm_validate_intel	Check whether a cache bit mask is valid. The SDM says:* Please note that all (and only) contiguous '1' combinations* are allowed (e.g. FFFFH, 0FF0H, 003CH, etc.).* Additionally Haswell requires at least two bits set.
cbm_validate_amd	Check whether a cache bit mask is valid. AMD allows non-contiguous* bitmasks
parse_cbm	Read one cache bit mask (hex). Check that it is valid for the current* resource type.
parse_line	For each domain in this resource we expect to find a series of:* id=mask* separated by ";". The "id" is in decimal, and must match one of* the "id"s for this resource.
rdtgroup_schemata_write
rdtgroup_schemata_show
pseudo_lock_cstates_constrain	pseudo_lock_cstates_constrain - Restrict cores from entering C6* To prevent the cache from being affected by power management entering* C6 has to be avoided
pseudo_lock_region_init	pseudo_lock_region_init - Initialize pseudo-lock region information@plr: pseudo-lock region Called after user provided a schemata to be pseudo-locked. From the* schemata the &struct pseudo_lock_region is on entry already initialized
pseudo_lock_region_alloc	pseudo_lock_region_alloc - Allocate kernel memory that will be pseudo-locked@plr: pseudo-lock region Initialize the details required to set up the pseudo-locked region and* allocate the contiguous memory that will be pseudo-locked to the cache.
rdtgroup_locksetup_enter	dtgroup_locksetup_enter - Resource group enters locksetup mode@rdtgrp: resource group requested to enter locksetup mode A resource group enters locksetup mode to reflect that it would be used* to represent a pseudo-locked region and is in the process of
rdtgroup_locksetup_exit	dtgroup_locksetup_exit - resource group exist locksetup mode@rdtgrp: resource group When a resource group exits locksetup mode the earlier restrictions are* lifted.* Return: 0 on success, <0 on failure
rdtgroup_pseudo_lock_create	dtgroup_pseudo_lock_create - Create a pseudo-locked region@rdtgrp: resource group to which pseudo-lock region belongs Called when a resource group in the pseudo-locksetup mode receives a* valid schemata that should be pseudo-locked

Function report