[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd7c3b6c-8e5a-6112-b825-ba17763a8094@linux.intel.com>
Date: Wed, 17 Apr 2024 16:13:52 +0300 (EEST)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Shravan Kumar Ramani <shravankr@...dia.com>
cc: Hans de Goede <hdegoede@...hat.com>, Vadim Pasternak <vadimp@...dia.com>,
David Thompson <davthompson@...dia.com>,
platform-driver-x86@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 1/3] Documentation/ABI: Add document for Mellanox PMC
driver
On Wed, 17 Apr 2024, Shravan Kumar Ramani wrote:
> The sysfs interface is created for programming and monitoring the
> performance counters in various HW blocks of Mellanox BlueField-1,
> BlueField-2 and BlueField-3.
>
> Signed-off-by: Shravan Kumar Ramani <shravankr@...dia.com>
> Reviewed-by: David Thompson <davthompson@...dia.com>
> ---
This documents the existing sysfs files? Which is good, thank you!
However, there's still no PATCH 4/ which would document the new interface
added by this series, namely use_odd_counter and count_clock, am I
correct?
--
i.
> .../ABI/testing/sysfs-platform-mellanox-pmc | 49 +++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-platform-mellanox-pmc
>
> diff --git a/Documentation/ABI/testing/sysfs-platform-mellanox-pmc b/Documentation/ABI/testing/sysfs-platform-mellanox-pmc
> new file mode 100644
> index 000000000000..47094024dbeb
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-platform-mellanox-pmc
> @@ -0,0 +1,49 @@
> +HID Driver Description
> +MLNXBFD0 mlxbf-pmc Performance counters (BlueField-1)
> +MLNXBFD1 mlxbf-pmc Performance counters (BlueField-2)
> +MLNXBFD2 mlxbf-pmc Performance counters (BlueField-3)
> +
> +What: /sys/bus/platform/devices/<HID>/hwmon/hwmonX/<block>/event_list
> +Date: Dec 2020
> +KernelVersion: 5.10
> +Contact: "Shravan Kumar Ramani <shravankr@...dia.com>"
> +Description:
> + List of events supported by the counters in the specific block.
> + It is used to extract the event number or ID associated with
> + each event.
> +
> +What: /sys/bus/platform/devices/<HID>/hwmon/hwmonX/<block>/event<N>
> +Date: Dec 2020
> +KernelVersion: 5.10
> +Contact: "Shravan Kumar Ramani <shravankr@...dia.com>"
> +Description:
> + Event monitored by corresponding counter. This is used to
> + program or read back the event that should be or is currently
> + being monitored by counter<N>.
> +
> +What: /sys/bus/platform/devices/<HID>/hwmon/hwmonX/<block>/counter<N>
> +Date: Dec 2020
> +KernelVersion: 5.10
> +Contact: "Shravan Kumar Ramani <shravankr@...dia.com>"
> +Description:
> + Counter value of the event being monitored. This is used to
> + read the counter value of the event which was programmed using
> + event<N>. This is also used to clear or reset the counter value.
> +
> +What: /sys/bus/platform/devices/<HID>/hwmon/hwmonX/<block>/enable
> +Date: Dec 2020
> +KernelVersion: 5.10
> +Contact: "Shravan Kumar Ramani <shravankr@...dia.com>"
> +Description:
> + Start or stop counters. This is used to start the counters
> + for monitoring the programmed events and also to stop the
> + counters after the desired duration.
> +
> +What: /sys/bus/platform/devices/<HID>/hwmon/hwmonX/<block>/<reg>
> +Date: Dec 2020
> +KernelVersion: 5.10
> +Contact: "Shravan Kumar Ramani <shravankr@...dia.com>"
> +Description:
> + Value of register. This is used to read or reset the registers
> + where various performance statistics are counted for each block.
> +
>
Powered by blists - more mailing lists