From: kbuild test robot <lkp@intel.com>
To: Prasad Sodagudi <psodagud@codeaurora.org>,
tglx@linutronix.de, john.stultz@linaro.org, sboyd@kernel.org,
tj@kernel.org
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
saravanak@google.com, psodagud@codeaurora.org,
pkondeti@codeaurora.org, Joonwoo Park <joonwoop@codeaurora.org>
Subject: Re: [PATCH v3 1/2] timer: make deferrable cpu unbound timers really not bound to a cpu
Date: Tue, 5 May 2020 02:11:10 +0800 [thread overview]
Message-ID: <202005050240.43QyO4uy%lkp@intel.com> (raw)
In-Reply-To: <1588444137-18651-2-git-send-email-psodagud@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 2895 bytes --]
Hi Prasad,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on tip/auto-latest tip/timers/nohz v5.7-rc4 next-20200501]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Prasad-Sodagudi/timer-make-deferrable-cpu-unbound-timers-really-not-bound-to-a-cpu/20200503-025049
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 4479730e9263befbb9ce9563a09563db2acb8f7c
config: riscv-nommu_virt_defconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/time/timer.c: In function 'get_timer_cpu_base':
>> kernel/time/timer.c:847:11: error: 'timer_base_deferrable' undeclared (first use in this function)
847 | base = &timer_base_deferrable;
| ^~~~~~~~~~~~~~~~~~~~~
kernel/time/timer.c:847:11: note: each undeclared identifier is reported only once for each function it appears in
kernel/time/timer.c: In function 'get_timer_this_cpu_base':
kernel/time/timer.c:866:11: error: 'timer_base_deferrable' undeclared (first use in this function)
866 | base = &timer_base_deferrable;
| ^~~~~~~~~~~~~~~~~~~~~
kernel/time/timer.c: In function 'run_timer_softirq':
kernel/time/timer.c:1805:18: error: 'timer_base_deferrable' undeclared (first use in this function)
1805 | __run_timers(&timer_base_deferrable);
| ^~~~~~~~~~~~~~~~~~~~~
vim +/timer_base_deferrable +847 kernel/time/timer.c
836
837 static inline struct timer_base *get_timer_cpu_base(u32 tflags, u32 cpu)
838 {
839 struct timer_base *base = per_cpu_ptr(&timer_bases[BASE_STD], cpu);
840
841 /*
842 * If the timer is deferrable and NO_HZ_COMMON is set then we need
843 * to use the deferrable base.
844 */
845 if (IS_ENABLED(CONFIG_NO_HZ_COMMON) && (tflags & TIMER_DEFERRABLE)) {
846 #ifdef CONFIG_SMP
> 847 base = &timer_base_deferrable;
848 #endif
849 if (tflags & TIMER_PINNED)
850 base = per_cpu_ptr(&timer_bases[BASE_DEF], cpu);
851 }
852
853 return base;
854 }
855
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6789 bytes --]
next prev parent reply other threads:[~2020-05-04 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 18:28 [PATCH v3 0/2] " Prasad Sodagudi
2020-05-02 18:28 ` [PATCH v3 1/2] " Prasad Sodagudi
2020-05-04 18:11 ` kbuild test robot [this message]
2020-05-05 0:08 ` kbuild test robot
2020-05-06 13:28 ` Thomas Gleixner
2020-05-13 19:53 ` psodagud
2020-05-13 20:28 ` Thomas Gleixner
2020-05-13 20:55 ` psodagud
2020-05-13 21:34 ` Thomas Gleixner
2020-05-02 18:28 ` [PATCH v3 2/2] sched: Add a check for cpu unbound deferrable timers Prasad Sodagudi
2020-05-04 19:11 ` kbuild test robot
2020-05-06 14:03 ` Thomas Gleixner
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=202005050240.43QyO4uy%lkp@intel.com \
--to=lkp@intel.com \
--cc=john.stultz@linaro.org \
--cc=joonwoop@codeaurora.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pkondeti@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@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®