On 4/18/23 06:34, Babu Moger wrote: > +"ctrl_hw_id": > + Available only with debug option. On x86, reading this file shows > + the Class of Service (CLOS) id which acts as a resource control > + tag on which the resources can be throttled. Kernel assigns a new > + CLOSID a control group is created depending on the available > + CLOSIDs. Multiple cores(or threads) or processes can share a > + same CLOSID in a resctrl group. > + > <snipped>... > +"mon_hw_id": > + Available only with debug option. On x86, reading this file shows > + the Resource Monitoring ID (RMID) for monitoring the resource > + utilization. Monitoring is performed by tagging each core (or > + thread) or process via a RMID. Kernel assigns a new RMID when > + a group is created depending on the available RMIDs. Multiple > + cores (or threads) or processes can share a same RMID in a > + resctrl group. > + Is CONFIG_DEBUG=y required? -- An old man doll... just what I always wanted! - Clara
