linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 1/2] timer: make deferrable cpu unbound timers really not bound to a cpu
Date: Wed, 29 Apr 2020 07:44:42 +0800	[thread overview]
Message-ID: <202004290721.QmYKQWvM%lkp@intel.com> (raw)
In-Reply-To: <1588104579-8712-2-git-send-email-psodagud@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 2519 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-rc3 next-20200428]
[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/20200429-060558
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 4479730e9263befbb9ce9563a09563db2acb8f7c
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

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 'run_timer_softirq':
>> kernel/time/timer.c:1804:18: error: 'timer_base_deferrable' undeclared (first use in this function); did you mean 'timer_base_lock_expiry'?
       __run_timers(&timer_base_deferrable);
                     ^~~~~~~~~~~~~~~~~~~~~
                     timer_base_lock_expiry
   kernel/time/timer.c:1804:18: note: each undeclared identifier is reported only once for each function it appears in
   kernel/time/timer.c: In function 'init_timer_deferrable_global':
   kernel/time/timer.c:2046:2: error: 'timer_base_deferrable' undeclared (first use in this function); did you mean 'timer_base_lock_expiry'?
     timer_base_deferrable.cpu = nr_cpu_ids;
     ^~~~~~~~~~~~~~~~~~~~~
     timer_base_lock_expiry

vim +1804 kernel/time/timer.c

  1791	
  1792	/*
  1793	 * This function runs timers and the timer-tq in bottom half context.
  1794	 */
  1795	static __latent_entropy void run_timer_softirq(struct softirq_action *h)
  1796	{
  1797		struct timer_base *base = this_cpu_ptr(&timer_bases[BASE_STD]);
  1798	
  1799		__run_timers(base);
  1800		if (IS_ENABLED(CONFIG_NO_HZ_COMMON)) {
  1801			__run_timers(this_cpu_ptr(&timer_bases[BASE_DEF]));
  1802			if (tick_do_timer_cpu == TICK_DO_TIMER_NONE ||
  1803					tick_do_timer_cpu == smp_processor_id())
> 1804				__run_timers(&timer_base_deferrable);
  1805		}
  1806	}
  1807	

---
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: 7238 bytes --]

  reply	other threads:[~2020-04-28 23:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 20:09 [PATCH v2 0/2] timer: make deferrable cpu unbound timers really not bound to a cpu Prasad Sodagudi
2020-04-28 20:09 ` [PATCH v2 1/2] " Prasad Sodagudi
2020-04-28 23:44   ` kbuild test robot [this message]
2020-04-28 20:09 ` [PATCH v2 2/2] sched: Add a check for cpu unbound deferrable timers Prasad Sodagudi
2020-04-28 23:29   ` kbuild test robot
2020-04-28 23:34   ` kbuild test robot

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=202004290721.QmYKQWvM%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;
as well as URLs for NNTP newsgroup(s).