From: kernel test robot <lkp@intel.com>
To: Oleg Nesterov <oleg@redhat.com>, Thomas Gleixner <tglx@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tick: shift tick_nohz_switch_to_nohz() from tick_check_oneshot_change() to hrtimer_run_queues()
Date: Fri, 31 May 2024 08:28:14 +0800 [thread overview]
Message-ID: <202405310818.JPmNHEjC-lkp@intel.com> (raw)
In-Reply-To: <20240530124203.GA26990@redhat.com>
Hi Oleg,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/timers/core]
[also build test ERROR on linus/master v6.10-rc1 next-20240529]
[cannot apply to tip/timers/nohz]
[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/Oleg-Nesterov/tick-shift-tick_nohz_switch_to_nohz-from-tick_check_oneshot_change-to-hrtimer_run_queues/20240530-204940
base: tip/timers/core
patch link: https://lore.kernel.org/r/20240530124203.GA26990%40redhat.com
patch subject: [PATCH] tick: shift tick_nohz_switch_to_nohz() from tick_check_oneshot_change() to hrtimer_run_queues()
config: i386-randconfig-001-20240531 (https://download.01.org/0day-ci/archive/20240531/202405310818.JPmNHEjC-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240531/202405310818.JPmNHEjC-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/202405310818.JPmNHEjC-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: kernel/time/hrtimer.o: in function `hrtimer_run_queues':
>> kernel/time/hrtimer.c:1898:(.text+0x1e71): undefined reference to `tick_nohz_switch_to_nohz'
vim +1898 kernel/time/hrtimer.c
1874
1875 /*
1876 * Called from run_local_timers in hardirq context every jiffy
1877 */
1878 void hrtimer_run_queues(void)
1879 {
1880 struct hrtimer_cpu_base *cpu_base = this_cpu_ptr(&hrtimer_bases);
1881 unsigned long flags;
1882 ktime_t now;
1883
1884 if (hrtimer_hres_active(cpu_base))
1885 return;
1886
1887 /*
1888 * This _is_ ugly: We have to check periodically, whether we
1889 * can switch to highres and / or nohz mode. The clocksource
1890 * switch happens with xtime_lock held. Notification from
1891 * there only sets the check bit in the tick_oneshot code,
1892 * otherwise we might deadlock vs. xtime_lock.
1893 */
1894 if (tick_check_oneshot_change()) {
1895 if (hrtimer_is_hres_enabled())
1896 hrtimer_switch_to_hres();
1897 else
> 1898 tick_nohz_switch_to_nohz();
1899 return;
1900 }
1901
1902 raw_spin_lock_irqsave(&cpu_base->lock, flags);
1903 now = hrtimer_update_base(cpu_base);
1904
1905 if (!ktime_before(now, cpu_base->softirq_expires_next)) {
1906 cpu_base->softirq_expires_next = KTIME_MAX;
1907 cpu_base->softirq_activated = 1;
1908 raise_softirq_irqoff(HRTIMER_SOFTIRQ);
1909 }
1910
1911 __hrtimer_run_queues(cpu_base, now, flags, HRTIMER_ACTIVE_HARD);
1912 raw_spin_unlock_irqrestore(&cpu_base->lock, flags);
1913 }
1914
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-31 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:42 Oleg Nesterov
2024-05-30 15:24 ` Frederic Weisbecker
2024-05-30 17:12 ` Oleg Nesterov
2024-06-01 14:56 ` Oleg Nesterov
2024-05-31 0:28 ` kernel test robot [this message]
2024-05-31 1:21 ` kernel test robot
2024-06-02 10:20 ` [PATCH v2] " Oleg Nesterov
2024-06-03 8:14 ` Thomas Gleixner
2024-06-03 13:41 ` Oleg Nesterov
2024-06-03 15:03 ` Oleg Nesterov
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=202405310818.JPmNHEjC-lkp@intel.com \
--to=lkp@intel.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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®