From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: linux-pm@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jiri Pirko <jiri@resnulli.us>,
Johannes Berg <johannes@sipsolutions.net>,
Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org
Subject: [PATCH v3 0/3] thermal/netlink/intel_hfi: Enable HFI feature only when required
Date: Fri, 9 Feb 2024 13:06:22 +0100 [thread overview]
Message-ID: <20240209120625.1775017-1-stanislaw.gruszka@linux.intel.com> (raw)
The patchset introduces a new genetlink family bind/unbind callbacks
and thermal/netlink notifications, which allow drivers to send netlink
multicast events based on the presence of actual user-space consumers.
This functionality optimizes resource usage by allowing disabling
of features when not needed.
Then implement the notification mechanism in the intel_hif driver,
it is utilized to disable the Hardware Feedback Interface (HFI)
dynamically. By implementing a thermal genl notify callback, the driver
can now enable or disable the HFI based on actual demand, particularly
when user-space applications like intel-speed-select or Intel Low Power
daemon utilize events related to performance and energy efficiency
capabilities.
On machines where Intel HFI is present, but there are no user-space
components installed, we can save tons of CPU cycles.
Changes v2 -> v3:
- Fix unused variable compilation warning
- Add missed Suggested by tag to patch2
Changes v1 -> v2:
- Rewrite using netlink_bind/netlink_unbind callbacks.
- Minor changelog tweaks.
- Add missing check in intel hfi syscore resume (had it on my testing,
but somehow missed in post).
- Do not use netlink_has_listeners() any longer, use custom counter instead.
To keep using netlink_has_listners() would be required to rearrange
netlink_setsockopt() and possibly netlink_bind() functions, to call
nlk->netlink_bind() after listeners are updated. So I decided to custom
counter. This have potential issue as thermal netlink registers before
intel_hif, so theoretically intel_hif can miss events. But since both
are required to be kernel build-in (if CONFIG_INTEL_HFI_THERMAL is
configured), they start before any user-space.
v1: https://lore.kernel.org/linux-pm/20240131120535.933424-1-stanislaw.gruszka@linux.intel.com//
v2: https://lore.kernel.org/linux-pm/20240206133605.1518373-1-stanislaw.gruszka@linux.intel.com/
Stanislaw Gruszka (3):
genetlink: Add per family bind/unbind callbacks
thermal: netlink: Add genetlink bind/unbind notifications
thermal: intel: hfi: Enable interface only when required
drivers/thermal/intel/intel_hfi.c | 95 +++++++++++++++++++++++++++----
drivers/thermal/thermal_netlink.c | 40 +++++++++++--
drivers/thermal/thermal_netlink.h | 25 ++++++++
include/net/genetlink.h | 4 ++
net/netlink/genetlink.c | 30 ++++++++++
5 files changed, 179 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-09 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 12:06 Stanislaw Gruszka [this message]
2024-02-09 12:06 ` [PATCH v3 1/3] genetlink: Add per family bind/unbind callbacks Stanislaw Gruszka
2024-02-09 12:06 ` [PATCH v3 2/3] thermal: netlink: Add genetlink bind/unbind notifications Stanislaw Gruszka
2024-02-09 18:28 ` Jakub Kicinski
2024-02-10 10:50 ` Stanislaw Gruszka
2024-02-09 12:06 ` [PATCH v3 3/3] thermal: intel: hfi: Enable interface only when required Stanislaw Gruszka
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=20240209120625.1775017-1-stanislaw.gruszka@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.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).