From: kernel test robot <lkp@intel.com>
To: Dimitri Sivanich <sivanich@hpe.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jiri Wiesner <jwiesner@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Jonathan Corbet <corbet@lwn.net>, Steve Wahl <steve.wahl@hpe.com>,
Justin Ernst <justin.ernst@hpe.com>,
Kyle Meyer <kyle.meyer@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2] x86/tsc: Disable clocksource watchdog for TSC on recent UV
Date: Fri, 8 Aug 2025 14:21:15 +0800 [thread overview]
Message-ID: <202508081446.3ZnRCG1T-lkp@intel.com> (raw)
In-Reply-To: <aJH9ke0k0HnL8g6h@hpe.com>
Hi Dimitri,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on tip/master linus/master v6.16 next-20250807]
[cannot apply to tip/auto-latest]
[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/Dimitri-Sivanich/x86-tsc-Disable-clocksource-watchdog-for-TSC-on-recent-UV/20250806-120227
base: tip/x86/core
patch link: https://lore.kernel.org/r/aJH9ke0k0HnL8g6h%40hpe.com
patch subject: [PATCH v2] x86/tsc: Disable clocksource watchdog for TSC on recent UV
config: i386-randconfig-011-20250808 (https://download.01.org/0day-ci/archive/20250808/202508081446.3ZnRCG1T-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250808/202508081446.3ZnRCG1T-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/202508081446.3ZnRCG1T-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/tsc.c:1264:39: error: call to undeclared function 'is_uvy_hub'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1264 | (topology_max_packages() <= 4 || is_uvy_hub()))
| ^
arch/x86/kernel/tsc.c:1517:6: error: call to undeclared function 'is_early_uv_system'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1517 | if (is_early_uv_system())
| ^
2 errors generated.
vim +/is_uvy_hub +1264 arch/x86/kernel/tsc.c
1235
1236 static void __init check_system_tsc_reliable(void)
1237 {
1238 #if defined(CONFIG_MGEODEGX1) || defined(CONFIG_MGEODE_LX) || defined(CONFIG_X86_GENERIC)
1239 if (is_geode_lx()) {
1240 /* RTSC counts during suspend */
1241 #define RTSC_SUSP 0x100
1242 unsigned long res_low, res_high;
1243
1244 rdmsr_safe(MSR_GEODE_BUSCONT_CONF0, &res_low, &res_high);
1245 /* Geode_LX - the OLPC CPU has a very reliable TSC */
1246 if (res_low & RTSC_SUSP)
1247 tsc_clocksource_reliable = 1;
1248 }
1249 #endif
1250 if (boot_cpu_has(X86_FEATURE_TSC_RELIABLE))
1251 tsc_clocksource_reliable = 1;
1252
1253 /*
1254 * Disable the clocksource watchdog when the system has:
1255 * - TSC running at constant frequency
1256 * - TSC which does not stop in C-States
1257 * - the TSC_ADJUST register which allows to detect even minimal
1258 * modifications
1259 * - not more than four packages
1260 */
1261 if (boot_cpu_has(X86_FEATURE_CONSTANT_TSC) &&
1262 boot_cpu_has(X86_FEATURE_NONSTOP_TSC) &&
1263 boot_cpu_has(X86_FEATURE_TSC_ADJUST) &&
> 1264 (topology_max_packages() <= 4 || is_uvy_hub()))
1265 tsc_disable_clocksource_watchdog();
1266 }
1267
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-08 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 12:48 Dimitri Sivanich
2025-08-08 6:21 ` kernel test robot [this message]
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=202508081446.3ZnRCG1T-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=justin.ernst@hpe.com \
--cc=jwiesner@suse.de \
--cc=kyle.meyer@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=russ.anderson@hpe.com \
--cc=sivanich@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=tglx@linutronix.de \
--cc=x86@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®