From: kernel test robot <lkp@intel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, Peter Zijlstra <peterz@infradead.org>
Subject: [peterz-queue:sched/eevdf 4/10] kernel/sched/fair.c:711: undefined reference to `__udivdi3'
Date: Sat, 4 Mar 2023 00:41:24 +0800 [thread overview]
Message-ID: <202303040023.GGyvAAAo-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/eevdf
head: bc35f40661d8d25ce8cde6e26d5956237a3e61ae
commit: bc9954a8f79988472545aa668a0be0dc5a0cddf3 [4/10] sched/fair: Add latency_offset
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20230304/202303040023.GGyvAAAo-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?id=bc9954a8f79988472545aa668a0be0dc5a0cddf3
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue sched/eevdf
git checkout bc9954a8f79988472545aa668a0be0dc5a0cddf3
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303040023.GGyvAAAo-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: kernel/sched/fair.o: in function `calc_latency_offset':
>> kernel/sched/fair.c:711: undefined reference to `__udivdi3'
vim +711 kernel/sched/fair.c
705
706 long calc_latency_offset(int prio)
707 {
708 u32 weight = sched_prio_to_weight[prio];
709 u64 base = sysctl_sched_min_granularity;
710
> 711 return (base << SCHED_FIXEDPOINT_SHIFT) / weight;
712 }
713
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-03 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202303040023.GGyvAAAo-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.