-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Automatic merge of 'next-test' into merge-test (2023-08-15 14:01)
- Loading branch information
Showing
102 changed files
with
1,728 additions
and
1,397 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -80,3 +80,163 @@ Contact: Linux on PowerPC Developer List <[email protected]> | |
Description: read only | ||
This sysfs file exposes the cpumask which is designated to make | ||
HCALLs to retrieve hv-gpci pmu event counter data. | ||
|
||
What: /sys/devices/hv_gpci/interface/processor_bus_topology | ||
Date: July 2023 | ||
Contact: Linux on PowerPC Developer List <[email protected]> | ||
Description: admin read only | ||
This sysfs file exposes the system topology information by making HCALL | ||
H_GET_PERF_COUNTER_INFO. The HCALL is made with counter request value | ||
PROCESSOR_BUS_TOPOLOGY(0xD0). | ||
|
||
* This sysfs file will be created only for power10 and above platforms. | ||
|
||
* User needs root privileges to read data from this sysfs file. | ||
|
||
* This sysfs file will be created, only when the HCALL returns "H_SUCCESS", | ||
"H_AUTHORITY" or "H_PARAMETER" as the return type. | ||
|
||
HCALL with return error type "H_AUTHORITY" can be resolved during | ||
runtime by setting "Enable Performance Information Collection" option. | ||
|
||
* The end user reading this sysfs file must decode the content as per | ||
underlying platform/firmware. | ||
|
||
Possible error codes while reading this sysfs file: | ||
|
||
* "-EPERM" : Partition is not permitted to retrieve performance information, | ||
required to set "Enable Performance Information Collection" option. | ||
|
||
* "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address | ||
or because of some hardware error. Refer to getPerfCountInfo documentation for | ||
more information. | ||
|
||
* "-EFBIG" : System information exceeds PAGE_SIZE. | ||
|
||
What: /sys/devices/hv_gpci/interface/processor_config | ||
Date: July 2023 | ||
Contact: Linux on PowerPC Developer List <[email protected]> | ||
Description: admin read only | ||
This sysfs file exposes the system topology information by making HCALL | ||
H_GET_PERF_COUNTER_INFO. The HCALL is made with counter request value | ||
PROCESSOR_CONFIG(0x90). | ||
|
||
* This sysfs file will be created only for power10 and above platforms. | ||
|
||
* User needs root privileges to read data from this sysfs file. | ||
|
||
* This sysfs file will be created, only when the HCALL returns "H_SUCCESS", | ||
"H_AUTHORITY" or "H_PARAMETER" as the return type. | ||
|
||
HCALL with return error type "H_AUTHORITY" can be resolved during | ||
runtime by setting "Enable Performance Information Collection" option. | ||
|
||
* The end user reading this sysfs file must decode the content as per | ||
underlying platform/firmware. | ||
|
||
Possible error codes while reading this sysfs file: | ||
|
||
* "-EPERM" : Partition is not permitted to retrieve performance information, | ||
required to set "Enable Performance Information Collection" option. | ||
|
||
* "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address | ||
or because of some hardware error. Refer to getPerfCountInfo documentation for | ||
more information. | ||
|
||
* "-EFBIG" : System information exceeds PAGE_SIZE. | ||
|
||
What: /sys/devices/hv_gpci/interface/affinity_domain_via_virtual_processor | ||
Date: July 2023 | ||
Contact: Linux on PowerPC Developer List <[email protected]> | ||
Description: admin read only | ||
This sysfs file exposes the system topology information by making HCALL | ||
H_GET_PERF_COUNTER_INFO. The HCALL is made with counter request value | ||
AFFINITY_DOMAIN_INFORMATION_BY_VIRTUAL_PROCESSOR(0xA0). | ||
|
||
* This sysfs file will be created only for power10 and above platforms. | ||
|
||
* User needs root privileges to read data from this sysfs file. | ||
|
||
* This sysfs file will be created, only when the HCALL returns "H_SUCCESS", | ||
"H_AUTHORITY" or "H_PARAMETER" as the return type. | ||
|
||
HCALL with return error type "H_AUTHORITY" can be resolved during | ||
runtime by setting "Enable Performance Information Collection" option. | ||
|
||
* The end user reading this sysfs file must decode the content as per | ||
underlying platform/firmware. | ||
|
||
Possible error codes while reading this sysfs file: | ||
|
||
* "-EPERM" : Partition is not permitted to retrieve performance information, | ||
required to set "Enable Performance Information Collection" option. | ||
|
||
* "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address | ||
or because of some hardware error. Refer to getPerfCountInfo documentation for | ||
more information. | ||
|
||
* "-EFBIG" : System information exceeds PAGE_SIZE. | ||
|
||
What: /sys/devices/hv_gpci/interface/affinity_domain_via_domain | ||
Date: July 2023 | ||
Contact: Linux on PowerPC Developer List <[email protected]> | ||
Description: admin read only | ||
This sysfs file exposes the system topology information by making HCALL | ||
H_GET_PERF_COUNTER_INFO. The HCALL is made with counter request value | ||
AFFINITY_DOMAIN_INFORMATION_BY_DOMAIN(0xB0). | ||
|
||
* This sysfs file will be created only for power10 and above platforms. | ||
|
||
* User needs root privileges to read data from this sysfs file. | ||
|
||
* This sysfs file will be created, only when the HCALL returns "H_SUCCESS", | ||
"H_AUTHORITY" or "H_PARAMETER" as the return type. | ||
|
||
HCALL with return error type "H_AUTHORITY" can be resolved during | ||
runtime by setting "Enable Performance Information Collection" option. | ||
|
||
* The end user reading this sysfs file must decode the content as per | ||
underlying platform/firmware. | ||
|
||
Possible error codes while reading this sysfs file: | ||
|
||
* "-EPERM" : Partition is not permitted to retrieve performance information, | ||
required to set "Enable Performance Information Collection" option. | ||
|
||
* "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address | ||
or because of some hardware error. Refer to getPerfCountInfo documentation for | ||
more information. | ||
|
||
* "-EFBIG" : System information exceeds PAGE_SIZE. | ||
|
||
What: /sys/devices/hv_gpci/interface/affinity_domain_via_partition | ||
Date: July 2023 | ||
Contact: Linux on PowerPC Developer List <[email protected]> | ||
Description: admin read only | ||
This sysfs file exposes the system topology information by making HCALL | ||
H_GET_PERF_COUNTER_INFO. The HCALL is made with counter request value | ||
AFFINITY_DOMAIN_INFORMATION_BY_PARTITION(0xB1). | ||
|
||
* This sysfs file will be created only for power10 and above platforms. | ||
|
||
* User needs root privileges to read data from this sysfs file. | ||
|
||
* This sysfs file will be created, only when the HCALL returns "H_SUCCESS", | ||
"H_AUTHORITY" or "H_PARAMETER" as the return type. | ||
|
||
HCALL with return error type "H_AUTHORITY" can be resolved during | ||
runtime by setting "Enable Performance Information Collection" option. | ||
|
||
* The end user reading this sysfs file must decode the content as per | ||
underlying platform/firmware. | ||
|
||
Possible error codes while reading this sysfs file: | ||
|
||
* "-EPERM" : Partition is not permitted to retrieve performance information, | ||
required to set "Enable Performance Information Collection" option. | ||
|
||
* "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address | ||
or because of some hardware error. Refer to getPerfCountInfo documentation for | ||
more information. | ||
|
||
* "-EFBIG" : System information exceeds PAGE_SIZE. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.