From: kernel test robot <lkp@intel.com>
To: James Morse <james.morse@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Shaopeng Tan <tan.shaopeng@fujitsu.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Babu Moger <babu.moger@amd.com>
Subject: [morse:mpam/monitors_and_locking/v8 24/24] ld.lld: error: undefined symbol: lockdep_is_cpus_held
Date: Sun, 17 Dec 2023 01:33:54 +0800 [thread overview]
Message-ID: <202312170155.WAkuJVpm-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/morse/linux.git mpam/monitors_and_locking/v8
head: b45f49cea5c2946c280481a479a2a9bd09a265be
commit: b45f49cea5c2946c280481a479a2a9bd09a265be [24/24] x86/resctrl: Separate arch and fs resctrl locks
config: x86_64-randconfig-002-20231216 (https://download.01.org/0day-ci/archive/20231217/202312170155.WAkuJVpm-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312170155.WAkuJVpm-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/202312170155.WAkuJVpm-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: lockdep_is_cpus_held
>>> referenced by core.c:374 (arch/x86/kernel/cpu/resctrl/core.c:374)
>>> arch/x86/kernel/cpu/resctrl/core.o:(get_domain_from_cpu) in archive vmlinux.a
>>> referenced by core.c:374 (arch/x86/kernel/cpu/resctrl/core.c:374)
>>> arch/x86/kernel/cpu/resctrl/core.o:(rdt_ctrl_update) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-16 17:34 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=202312170155.WAkuJVpm-lkp@intel.com \
--to=lkp@intel.com \
--cc=babu.moger@amd.com \
--cc=james.morse@arm.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=reinette.chatre@intel.com \
--cc=tan.shaopeng@fujitsu.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