From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH net-next V2 0/2] mlx5: Expose NIC temperature via hwmon API
Date: Mon, 7 Aug 2023 11:05:05 -0700 [thread overview]
Message-ID: <20230807180507.22984-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
V1->V2:
- Remove internal tracker tags
- Remove sanitized mlx5 sensor names
- add HWMON dependency in the mlx5 Kconfig
Expose NIC temperature by implementing hwmon kernel API, which turns
current thermal zone kernel API to redundant.
For each one of the supported and exposed thermal diode sensors, expose
the following attributes:
1) Input temperature.
2) Highest temperature.
3) Temperature label.
4) Temperature critical max value:
refers to the high threshold of Warning Event. Will be exposed as
`tempY_crit` hwmon attribute (RO attribute). For example for
ConnectX5 HCA's this temperature value will be 105 Celsius, 10
degrees lower than the HW shutdown temperature).
5) Temperature reset history: resets highest temperature.
Adham Faris (2):
net/mlx5: Expose port.c/mlx5_query_module_num() function
net/mlx5: Expose NIC temperature via hardware monitoring kernel API
.../net/ethernet/mellanox/mlx5/core/Kconfig | 1 +
.../net/ethernet/mellanox/mlx5/core/Makefile | 2 +-
.../net/ethernet/mellanox/mlx5/core/hwmon.c | 418 ++++++++++++++++++
.../net/ethernet/mellanox/mlx5/core/hwmon.h | 24 +
.../net/ethernet/mellanox/mlx5/core/main.c | 8 +-
.../ethernet/mellanox/mlx5/core/mlx5_core.h | 1 +
.../net/ethernet/mellanox/mlx5/core/port.c | 2 +-
.../net/ethernet/mellanox/mlx5/core/thermal.c | 114 -----
.../net/ethernet/mellanox/mlx5/core/thermal.h | 20 -
include/linux/mlx5/driver.h | 3 +-
include/linux/mlx5/mlx5_ifc.h | 14 +-
11 files changed, 465 insertions(+), 142 deletions(-)
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/hwmon.c
create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/hwmon.h
delete mode 100644 drivers/net/ethernet/mellanox/mlx5/core/thermal.c
delete mode 100644 drivers/net/ethernet/mellanox/mlx5/core/thermal.h
--
2.41.0
next reply other threads:[~2023-08-07 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 18:05 Saeed Mahameed [this message]
2023-08-07 18:05 ` [PATCH net-next V2 1/2] net/mlx5: Expose port.c/mlx5_query_module_num() function Saeed Mahameed
2023-08-07 18:05 ` [PATCH net-next V2 2/2] net/mlx5: Expose NIC temperature via hardware monitoring kernel API Saeed Mahameed
2023-08-09 17:54 ` Guenter Roeck
2023-08-08 20:07 ` [PATCH net-next V2 0/2] mlx5: Expose NIC temperature via hwmon API Simon Horman
2023-08-09 23:00 ` patchwork-bot+netdevbpf
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=20230807180507.22984-1-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/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).