From: Kajol Jain <kjain@linux.ibm.com>
To: mpe@ellerman.id.au
Cc: disgoel@linux.ibm.com, kjain@linux.ibm.com,
atrajeev@linux.vnet.ibm.com, maddy@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 10/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_partition sysfs interface file
Date: Fri, 9 Jun 2023 17:10:01 +0530 [thread overview]
Message-ID: <20230609114001.169235-11-kjain@linux.ibm.com> (raw)
In-Reply-To: <20230609114001.169235-1-kjain@linux.ibm.com>
Add details of the new hv-gpci interface file called
"affinity_domain_via_partition" in the ABI documentation.
Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
---
.../sysfs-bus-event_source-devices-hv_gpci | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci
index 1a5636ed3a4b..6bca74cf3220 100644
--- a/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci
+++ b/Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci
@@ -154,3 +154,18 @@ Description: admin read only
removed, this sysfs file still be created and give error when reading it.
* The end user reading this sysfs file need to decode sysfs file data as per
underneath platform/firmware.
+
+What: /sys/devices/hv_gpci/interface/affinity_domain_via_partition
+Date: June 2023
+Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
+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 is only be created for power10 and above platforms.
+ * User need root access to read data from this sysfs file.
+ * Incase the HCALL fails with hardware/permission issue, or the support for
+ AFFINITY_DOMAIN_INFORMATION_BY_PARTITION counter request value
+ removed, this sysfs file still be created and give error when reading it.
+ * The end user reading this sysfs file need to decode sysfs file data as per
+ underneath platform/firmware.
--
2.35.3
prev parent reply other threads:[~2023-06-09 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:39 [PATCH 00/10] Add sysfs interface files to hv_gpci device to expose system information Kajol Jain
2023-06-09 11:39 ` [PATCH 01/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show processor bus topology information Kajol Jain
2023-06-09 11:39 ` [PATCH 02/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document processor_bus_topology sysfs interface file Kajol Jain
2023-06-09 11:39 ` [PATCH 03/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show processor config information Kajol Jain
2023-06-09 11:39 ` [PATCH 04/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document processor_config sysfs interface file Kajol Jain
2023-06-09 11:39 ` [PATCH 05/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via virtual processor information Kajol Jain
2023-06-09 11:39 ` [PATCH 06/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_virtual_processor sysfs interface file Kajol Jain
2023-06-09 11:39 ` [PATCH 07/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via domain information Kajol Jain
2023-06-09 11:39 ` [PATCH 08/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_domain sysfs interface file Kajol Jain
2023-06-09 11:40 ` [PATCH 09/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via partition information Kajol Jain
2023-06-09 11:40 ` Kajol Jain [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230609114001.169235-11-kjain@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).