From: kernel test robot <lkp@intel.com>
To: Pierre Gondois <pierre.gondois@arm.com>, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jie Zhan <zhanjie9@hisilicon.com>,
zhenglifeng1@huawei.com,
Ionela Voinescu <ionela.voinescu@arm.com>,
Christian Loehle <christian.loehle@arm.com>,
sumitg@nvidia.com, Pierre Gondois <pierre.gondois@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Huang Rui <ray.huang@amd.com>,
"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Perry Yuan <perry.yuan@amd.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 5/6] cpufreq: Set policy->min and max as real QoS constraints
Date: Thu, 29 Jan 2026 14:02:43 +0800 [thread overview]
Message-ID: <202601291343.bghsD4zH-lkp@intel.com> (raw)
In-Reply-To: <20260126101826.94030-6-pierre.gondois@arm.com>
Hi Pierre,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.19-rc7 next-20260128]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Pierre-Gondois/cpufreq-Remove-per-CPU-QoS-constraint/20260126-182440
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20260126101826.94030-6-pierre.gondois%40arm.com
patch subject: [PATCH 5/6] cpufreq: Set policy->min and max as real QoS constraints
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20260129/202601291343.bghsD4zH-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260129/202601291343.bghsD4zH-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601291343.bghsD4zH-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpufreq/virtual-cpufreq.c:167:19: warning: expression result unused [-Wunused-value]
policy->cpuinfo.min_freq;
~~~~~~~~~~~~~~~ ^~~~~~~~
drivers/cpufreq/virtual-cpufreq.c:168:19: warning: expression result unused [-Wunused-value]
policy->cpuinfo.max_freq;
~~~~~~~~~~~~~~~ ^~~~~~~~
2 warnings generated.
vim +167 drivers/cpufreq/virtual-cpufreq.c
155
156 static int virt_cpufreq_get_freq_info(struct cpufreq_policy *policy)
157 {
158 struct cpufreq_frequency_table *table;
159 u32 num_perftbl_entries, idx;
160
161 num_perftbl_entries = per_cpu(perftbl_num_entries, policy->cpu);
162
163 if (num_perftbl_entries == 1) {
164 policy->cpuinfo.min_freq = 1;
165 policy->cpuinfo.max_freq = virt_cpufreq_get_perftbl_entry(policy->cpu, 0);
166
> 167 policy->cpuinfo.min_freq;
168 policy->cpuinfo.max_freq;
169
170 policy->cur = policy->cpuinfo.max_freq;
171 return 0;
172 }
173
174 table = kcalloc(num_perftbl_entries + 1, sizeof(*table), GFP_KERNEL);
175 if (!table)
176 return -ENOMEM;
177
178 for (idx = 0; idx < num_perftbl_entries; idx++)
179 table[idx].frequency = virt_cpufreq_get_perftbl_entry(policy->cpu, idx);
180
181 table[idx].frequency = CPUFREQ_TABLE_END;
182 policy->freq_table = table;
183
184 return 0;
185 }
186
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-29 6:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 10:18 [PATCH 0/6] cpufreq: Introduce boost frequency QoS Pierre Gondois
2026-01-26 10:18 ` [PATCH 1/6] cpufreq: Remove per-CPU QoS constraint Pierre Gondois
2026-01-31 3:28 ` zhenglifeng (A)
2026-02-05 13:59 ` Pierre Gondois
2026-02-06 7:17 ` zhenglifeng (A)
2026-01-26 10:18 ` [PATCH 2/6] cpufreq: Add boost_freq_req QoS request Pierre Gondois
2026-01-31 4:00 ` zhenglifeng (A)
2026-02-05 13:58 ` Pierre Gondois
2026-01-26 10:18 ` [PATCH 3/6] cpufreq: Centralize boost freq QoS requests Pierre Gondois
2026-01-31 4:11 ` zhenglifeng (A)
2026-02-05 13:58 ` Pierre Gondois
2026-01-26 10:18 ` [PATCH 4/6] cpufreq: Update .set_boost() callbacks to rely on boost_freq_req Pierre Gondois
2026-01-26 10:18 ` [PATCH 5/6] cpufreq: Set policy->min and max as real QoS constraints Pierre Gondois
2026-01-29 6:02 ` kernel test robot [this message]
2026-01-29 9:52 ` kernel test robot
2026-01-26 10:18 ` [RFC PATCH 6/6] cpufreq/freq_table: Allow decreasing cpuinfo.max_freq Pierre Gondois
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=202601291343.bghsD4zH-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.loehle@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=ionela.voinescu@arm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mario.limonciello@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=perry.yuan@amd.com \
--cc=pierre.gondois@arm.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=saravanak@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumitg@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.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