From: kernel test robot <lkp@intel.com>
To: Joel Fernandes <joelaf@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: kernel/time/tick-sched.c:995: warning: Function parameter or member 'cpu' not described in 'tick_nohz_get_idle_calls_cpu'
Date: Thu, 16 Nov 2023 12:45:18 +0800 [thread overview]
Message-ID: <202311161213.8QKZqSLs-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c42d9eeef8e5ba9292eda36fd8e3c11f35ee065c
commit: 466a2b42d67644447a1765276259a3ea5531ddff cpufreq: schedutil: Use idle_calls counter of the remote CPU
date: 6 years ago
config: x86_64-randconfig-x012-20230629 (https://download.01.org/0day-ci/archive/20231116/202311161213.8QKZqSLs-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231116/202311161213.8QKZqSLs-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/202311161213.8QKZqSLs-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/x86/include/asm/bitops.h: Assembler messages:
arch/x86/include/asm/bitops.h:225: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:271: Warning: no instruction mnemonic suffix given and no register operands; using default for `btr'
arch/x86/include/asm/bitops.h:225: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
kernel/time/tick-sched.c:500: warning: Function parameter or member 'now' not described in 'tick_nohz_update_jiffies'
>> kernel/time/tick-sched.c:995: warning: Function parameter or member 'cpu' not described in 'tick_nohz_get_idle_calls_cpu'
kernel/time/tick-sched.c:1248: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Async notification about clocksource changes
kernel/time/tick-sched.c:1269: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Check, if a change happened, which makes oneshot possible.
kernel/time/tick-sched.o: warning: objtool: tick_nohz_stop_sched_tick()+0xb1a: sibling call from callable instruction with modified stack frame
kernel/time/tick-sched.o: warning: objtool: __tick_nohz_idle_enter()+0x398: sibling call from callable instruction with modified stack frame
kernel/time/tick-sched.o: warning: objtool: tick_do_update_jiffies64.part.0()+0x2a4: sibling call from callable instruction with modified stack frame
kernel/time/tick-sched.o: warning: objtool: tick_nohz_idle_enter()+0x13f: sibling call from callable instruction with modified stack frame
kernel/time/tick-sched.o: warning: objtool: tick_setup_sched_timer()+0x227: sibling call from callable instruction with modified stack frame
kernel/time/tick-sched.o: warning: objtool: tick_check_oneshot_change()+0x8d: sibling call from callable instruction with modified stack frame
vim +995 kernel/time/tick-sched.c
987
988 /**
989 * tick_nohz_get_idle_calls_cpu - return the current idle calls counter value
990 * for a particular CPU.
991 *
992 * Called from the schedutil frequency scaling governor in scheduler context.
993 */
994 unsigned long tick_nohz_get_idle_calls_cpu(int cpu)
> 995 {
996 struct tick_sched *ts = tick_get_tick_sched(cpu);
997
998 return ts->idle_calls;
999 }
1000
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-16 4:46 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=202311161213.8QKZqSLs-lkp@intel.com \
--to=lkp@intel.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rjw@rjwysocki.net \
/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®