From: kernel test robot <lkp@intel.com>
To: Tim Bird <tim.bird@sony.com>,
pmladek@suse.com, rostedt@goodmis.org, john.ogness@linutronix.de,
senozhatsky@chromium.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
francesco@valla.it, geert@linux-m68k.org, tglx@kernel.org,
shashankbalaji02@gmail.com, linux-embedded@vger.kernel.org,
linux-kernel@vger.kernel.org, Tim Bird <tim.bird@sony.com>
Subject: Re: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot
Date: Sun, 12 Apr 2026 20:55:30 +0800 [thread overview]
Message-ID: <202604122037.R14cnXpl-lkp@intel.com> (raw)
In-Reply-To: <20260410203741.997410-2-tim.bird@sony.com>
Hi Tim,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc7 next-20260410]
[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/Tim-Bird/printk-fix-zero-valued-printk-timestamps-in-early-boot/20260412-134726
base: linus/master
patch link: https://lore.kernel.org/r/20260410203741.997410-2-tim.bird%40sony.com
patch subject: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot
config: um-defconfig (https://download.01.org/0day-ci/archive/20260412/202604122037.R14cnXpl-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project ae825cb8cea7f3ac8e5e4096f22713845cf5e501)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260412/202604122037.R14cnXpl-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/202604122037.R14cnXpl-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/printk/printk.c:49:
>> include/linux/early_times.h:20:9: error: call to undeclared function 'rdtsc'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
20 | return rdtsc();
| ^
include/linux/early_times.h:45:47: warning: division by zero is undefined [-Wdivision-by-zero]
45 | return (early_unsafe_cycles() * NS_PER_KHZ) / CONFIG_EARLY_CYCLES_KHZ;
| ^ ~~~~~~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.
vim +/rdtsc +20 include/linux/early_times.h
10
11 #ifdef CONFIG_EARLY_CYCLES_KHZ
12 static inline u64 early_unsafe_cycles(void)
13 {
14 #if defined(CONFIG_X86_64)
15 /*
16 * This rdtsc may happen before secure TSC is initialized, and
17 * it is unordered. So please don't use this value for cryptography
18 * or after SMP is initialized.
19 */
> 20 return rdtsc();
21 #elif defined(CONFIG_ARM64)
22 return read_sysreg(cntvct_el0);
23 #elif defined(CONFIG_RISCV_TIMER)
24 u64 val;
25
26 asm volatile("rdtime %0" : "=r"(val));
27 return val;
28 #else
29 return 0;
30 #endif
31 }
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-04-12 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260410203741.997410-2-tim.bird@sony.com>
2026-04-12 11:12 ` [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot kernel test robot
2026-04-12 12:55 ` 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=202604122037.R14cnXpl-lkp@intel.com \
--to=lkp@intel.com \
--cc=francesco@valla.it \
--cc=geert@linux-m68k.org \
--cc=john.ogness@linutronix.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=shashankbalaji02@gmail.com \
--cc=tglx@kernel.org \
--cc=tim.bird@sony.com \
/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