From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Aubrey Li <aubrey.li@linux.intel.com>,
Amit Kucheria <amitk@kernel.org>, Andi Kleen <ak@linux.intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
Ricardo Neri <ricardo.neri@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH v5 6/7] thermal: netlink: Add a new event to notify CPU capabilities change
Date: Thu, 10 Feb 2022 11:22:02 +0000 [thread overview]
Message-ID: <ede29257-d356-9fc6-5f1a-c42721c0d072@arm.com> (raw)
In-Reply-To: <CAJZ5v0hbtmP6LHngWg0J47G2PwTxNwmjb=KMyz1zi1FM09cF8g@mail.gmail.com>
On 1/30/22 3:20 PM, Rafael J. Wysocki wrote:
> On Thu, Jan 27, 2022 at 8:33 PM Ricardo Neri
> <ricardo.neri-calderon@linux.intel.com> wrote:
>>
>> From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>>
>> Add a new netlink event to notify change in CPU capabilities in terms of
>> performance and efficiency.
>>
>> Firmware may change CPU capabilities as a result of thermal events in the
>> system or to account for changes in the TDP (thermal design power) level.
>>
>> This notification type will allow user space to avoid running workloads
>> on certain CPUs or proactively adjust power limits to avoid future events.
>>
>> The netlink message consists of a nested attribute
>> (THERMAL_GENL_ATTR_CPU_CAPABILITY) with three attributes:
>>
>> * THERMAL_GENL_ATTR_CPU_CAPABILITY_ID (type u32):
>> -- logical CPU number
>> * THERMAL_GENL_ATTR_CPU_CAPABILITY_PERFORMANCE (type u32):
>> -- Scaled performance from 0-1023
>> * THERMAL_GENL_ATTR_CPU_CAPABILITY_EFFICIENCY (type u32):
>> -- Scaled efficiency from 0-1023
>>
>> Cc: Andi Kleen <ak@linux.intel.com>
>> Cc: Aubrey Li <aubrey.li@linux.intel.com>
>> Cc: Lukasz Luba <lukasz.luba@arm.com>
>> Cc: Tim Chen <tim.c.chen@linux.intel.com>
>> Cc: "Ravi V. Shankar" <ravi.v.shankar@intel.com>
>> Reviewed-by: Len Brown <len.brown@intel.com>
>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>
> Daniel, Lukasz, if you have any comments or concerns regarding this
> patch, please let me know.
>
My apologies Rafael, I missed that email.
I've looked at the patches 6/7 and 7/7 and they look OK with the
scaling.
next prev parent reply other threads:[~2022-02-10 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 19:34 [PATCH v5 0/7] Thermal: Introduce the Hardware Feedback Interface for thermal and performance management Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 1/7] x86/Documentation: Describe the Intel Hardware Feedback Interface Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 2/7] x86/cpu: Add definitions for " Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 3/7] thermal: intel: hfi: Minimally initialize the " Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 4/7] thermal: intel: hfi: Handle CPU hotplug events Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 5/7] thermal: intel: hfi: Enable notification interrupt Ricardo Neri
2022-01-27 19:34 ` [PATCH v5 6/7] thermal: netlink: Add a new event to notify CPU capabilities change Ricardo Neri
2022-01-30 15:20 ` Rafael J. Wysocki
2022-02-10 11:22 ` Lukasz Luba [this message]
2022-01-27 19:34 ` [PATCH v5 7/7] thermal: intel: hfi: Notify user space for HFI events Ricardo Neri
2022-01-30 15:23 ` [PATCH v5 0/7] Thermal: Introduce the Hardware Feedback Interface for thermal and performance management Rafael J. Wysocki
2022-02-03 18:57 ` Rafael J. Wysocki
2022-02-05 0:47 ` Ricardo Neri
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=ede29257-d356-9fc6-5f1a-c42721c0d072@arm.com \
--to=lukasz.luba@arm.com \
--cc=ak@linux.intel.com \
--cc=amitk@kernel.org \
--cc=aubrey.li@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®