| 1 | What: /sys/kernel/debug/tpmi-<n>/pfs_dump |
| 2 | Date: November 2023 |
| 3 | KernelVersion: 6.6 |
| 4 | Contact: [email protected] |
| 5 | Description: |
| 6 | The PFS (PM Feature Structure) table, shows details of each power |
| 7 | management feature. This includes: |
| 8 | tpmi_id, number of entries, entry size, offset, vsec offset, lock status |
| 9 | and disabled status. |
| 10 | Users: Debugging, any user space test suite |
| 11 | |
| 12 | What: /sys/kernel/debug/tpmi-<n>/tpmi-id-<n>/mem_dump |
| 13 | Date: November 2023 |
| 14 | KernelVersion: 6.6 |
| 15 | Contact: [email protected] |
| 16 | Description: |
| 17 | Shows the memory dump of the MMIO region for a TPMI ID. |
| 18 | Users: Debugging, any user space test suite |
| 19 | |
| 20 | What: /sys/kernel/debug/tpmi-<n>/tpmi-id-<n>/mem_write |
| 21 | Date: November 2023 |
| 22 | KernelVersion: 6.6 |
| 23 | Contact: [email protected] |
| 24 | Description: |
| 25 | Allows to write at any offset. It doesn't check for Read/Write access |
| 26 | as hardware will not allow to write at read-only memory. This write is |
| 27 | at offset multiples of 4. The format is instance,offset,contents. |
| 28 | Example: |
| 29 | echo 0,0x20,0xff > mem_write |
| 30 | echo 1,64,64 > mem_write |
| 31 | Users: Debugging, any user space test suite |
| 32 | |
| 33 | What: /sys/kernel/debug/tpmi-<n>/plr/domain<n>/status |
| 34 | Date: Aug 2024 |
| 35 | KernelVersion: 6.11 |
| 36 | Contact: Tero Kristo <[email protected]> |
| 37 | Description: |
| 38 | Shows the currently active Performance Limit Reasons for die level and the |
| 39 | individual CPUs under the die. The contents of this file are sticky, and |
| 40 | clearing all the statuses can be done by writing "0\n" to this file. |