From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Kajol Jain <kjain@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
disgoel@linux.ibm.com, linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3 00/10] Add sysfs interface files to hv_gpci device to expose system information
Date: Tue, 25 Jul 2023 11:23:23 +0530 [thread overview]
Message-ID: <D884EDCC-EC77-4C80-A4D4-06B50ABE4AF8@linux.vnet.ibm.com> (raw)
In-Reply-To: <20230719061231.631410-1-kjain@linux.ibm.com>
> On 19-Jul-2023, at 11:42 AM, Kajol Jain <kjain@linux.ibm.com> wrote:
>
> The hcall H_GET_PERF_COUNTER_INFO can be used to get data related to
> chips, dimms and system topology, by passing different counter request
> values.
> Patchset adds sysfs files to "/sys/devices/hv_gpci/interface/"
> of hv_gpci pmu driver, which will expose system topology information
> using H_GET_PERF_COUNTER_INFO hcall. The added sysfs files are
> available for power10 and above platforms and needs root access
> to read the data.
>
> Patches 1,3,5,7,9 adds sysfs interface files to the hv_gpci
> pmu driver, to get system topology information.
>
> List of added sysfs files:
> -> processor_bus_topology (Counter request value : 0xD0)
> -> processor_config (Counter request value : 0x90)
> -> affinity_domain_via_virtual_processor (Counter request value : 0xA0)
> -> affinity_domain_via_domain (Counter request value : 0xB0)
> -> affinity_domain_via_partition (Counter request value : 0xB1)
>
> Patches 2,4,6,8,10 adds details of the newly added hv_gpci
> interface files listed above in the ABI documentation.
>
> Patches 2,4,6,8,10 adds details of the newly added hv_gpci
> interface files listed above in the ABI documentation.
Reviewed-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
Thanks
Athira
>
> Changelog:
> v2 -> v3
> -> Make nit changes in documentation patches as suggested by Randy Dunlap.
>
> v1 -> v2
> -> Incase the HCALL fails with errors that can be resolve during runtime,
> then only add sysinfo interface attributes to the interface_attrs
> attribute array. Even if one of the counter request value HCALL fails,
> don't add any sysinfo attribute to the interface_attrs attribute array.
> Add the code changes to make sure sysinfo interface added only when all
> the requirements met as suggested by Michael Ellerman.
> -> Make changes in documentation, adds detail of errors type
> which can be resolved at runtime as suggested by Michael Ellerman.
> -> Add new enum and sysinfo_counter_request array to get required
> counter request value in hv-gpci.c file.
> -> Move the macros for interface attribute array index to hv-gpci.c, as
> these macros currently only used in hv-gpci.c file.
>
> Kajol Jain (10):
> powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show
> processor bus topology information
> docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document
> processor_bus_topology sysfs interface file
> powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show
> processor config information
> docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document
> processor_config sysfs interface file
> powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity
> domain via virtual processor information
> docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document
> affinity_domain_via_virtual_processor sysfs interface file
> powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity
> domain via domain information
> docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document
> affinity_domain_via_domain sysfs interface file
> powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity
> domain via partition information
> docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document
> affinity_domain_via_partition sysfs interface file
>
> .../sysfs-bus-event_source-devices-hv_gpci | 160 +++++
> arch/powerpc/perf/hv-gpci.c | 640 +++++++++++++++++-
> 2 files changed, 798 insertions(+), 2 deletions(-)
>
> --
> 2.39.3
>
next prev parent reply other threads:[~2023-07-25 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 6:12 [PATCH v3 00/10] Add sysfs interface files to hv_gpci device to expose system information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 01/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show processor bus topology information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 02/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document processor_bus_topology sysfs interface file Kajol Jain
2023-07-19 6:12 ` [PATCH v3 03/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show processor config information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 04/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document processor_config sysfs interface file Kajol Jain
2023-07-19 6:12 ` [PATCH v3 05/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via virtual processor information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 06/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_virtual_processor sysfs interface file Kajol Jain
2023-07-19 6:12 ` [PATCH v3 07/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via domain information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 08/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_domain sysfs interface file Kajol Jain
2023-07-19 6:12 ` [PATCH v3 09/10] powerpc/hv_gpci: Add sysfs file inside hv_gpci device to show affinity domain via partition information Kajol Jain
2023-07-19 6:12 ` [PATCH v3 10/10] docs: ABI: sysfs-bus-event_source-devices-hv_gpci: Document affinity_domain_via_partition sysfs interface file Kajol Jain
2023-07-25 5:53 ` Athira Rajeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-19 6:06 [PATCH v3 00/10] Add sysfs interface files to hv_gpci device to expose system information Kajol Jain
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=D884EDCC-EC77-4C80-A4D4-06B50ABE4AF8@linux.vnet.ibm.com \
--to=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.ibm.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rdunlap@infradead.org \
/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).