[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231025093847.3740104-1-zengheng4@huawei.com>
Date: Wed, 25 Oct 2023 17:38:44 +0800
From: Zeng Heng <zengheng4@...wei.com>
To: <broonie@...nel.org>, <joey.gouly@....com>, <will@...nel.org>,
<amit.kachhap@....com>, <rafael@...nel.org>,
<catalin.marinas@....com>, <james.morse@....com>,
<mark.rutland@....com>, <maz@...nel.org>,
<viresh.kumar@...aro.org>, <sumitg@...dia.com>,
<yang@...amperecomputing.com>
CC: <linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<wangxiongfeng2@...wei.com>, <xiexiuqi@...wei.com>
Subject: [PATCH 0/3] Make the cpuinfo_cur_freq interface read correctly
Patch 1~2: It is required to ensure that amu can continue to work normally
during the sample period while cstate is enabled.
Patch 3: Even works in the mmio mode, cpc_read still has random delay
errors, so let's extend the sampling time.
Zeng Heng (3):
arm64: cpufeature: Export cpu_has_amu_feat()
cpufreq: CPPC: Keep the target core awake when reading its cpufreq
rate
cpufreq: CPPC: Eliminate the impact of cpc_read() latency error
arch/arm64/kernel/cpufeature.c | 1 +
drivers/cpufreq/cppc_cpufreq.c | 53 ++++++++++++++++++++++++++++------
2 files changed, 45 insertions(+), 9 deletions(-)
--
2.25.1
Powered by blists - more mailing lists