From: kernel test robot <lkp@intel.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [qais-yousef:sched-setscheduler-hide 6/9] drivers/cpufreq/cppc_cpufreq.c:242:15: error: too few arguments to function 'sched_set_dl'
Date: Sat, 26 Aug 2023 20:23:18 +0800 [thread overview]
Message-ID: <202308262003.40lCLvIm-lkp@intel.com> (raw)
tree: https://github.com/qais-yousef/linux sched-setscheduler-hide
head: e586c67baa1c537a793f135e324cc56df2b6585b
commit: d70e8ba918c698ee2b48006d483001b8a345ad62 [6/9] cpufreq: cppc: Convert to use sched_set_dl()
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20230826/202308262003.40lCLvIm-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230826/202308262003.40lCLvIm-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/202308262003.40lCLvIm-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/cpufreq/cppc_cpufreq.c: In function 'cppc_freq_invariance_init':
>> drivers/cpufreq/cppc_cpufreq.c:242:15: error: too few arguments to function 'sched_set_dl'
242 | ret = sched_set_dl(kworker_fie->task);
| ^~~~~~~~~~~~
In file included from arch/arm64/include/asm/compat.h:28,
from arch/arm64/include/asm/stat.h:13,
from include/linux/stat.h:6,
from include/linux/module.h:13,
from drivers/cpufreq/cppc_cpufreq.c:15:
include/linux/sched.h:1920:13: note: declared here
1920 | extern void sched_set_dl(struct task_struct *p, unsigned long long flags);
| ^~~~~~~~~~~~
vim +/sched_set_dl +242 drivers/cpufreq/cppc_cpufreq.c
222
223 static void __init cppc_freq_invariance_init(void)
224 {
225 int ret;
226
227 if (fie_disabled != FIE_ENABLED && fie_disabled != FIE_DISABLED) {
228 fie_disabled = FIE_ENABLED;
229 if (cppc_perf_ctrs_in_pcc()) {
230 pr_info("FIE not enabled on systems with registers in PCC\n");
231 fie_disabled = FIE_DISABLED;
232 }
233 }
234
235 if (fie_disabled)
236 return;
237
238 kworker_fie = kthread_create_worker(0, "cppc_fie");
239 if (IS_ERR(kworker_fie))
240 return;
241
> 242 ret = sched_set_dl(kworker_fie->task);
243 if (ret) {
244 pr_warn("%s: failed to set SCHED_DEADLINE: %d\n", __func__,
245 ret);
246 kthread_destroy_worker(kworker_fie);
247 return;
248 }
249 }
250
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-26 12:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202308262003.40lCLvIm-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qyousef@layalina.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.