From: kernel test robot <lkp@intel.com>
To: Dexuan Cui <decui@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Michael Kelley <mikelley@microsoft.com>
Subject: [dcui-tdx:decui/upstream-tip/x86/tdx/v7-wip 7/15] arch/x86/hyperv/ivm.c:427: undefined reference to `__tdx_hypercall_ret'
Date: Sat, 17 Jun 2023 14:59:19 +0800 [thread overview]
Message-ID: <202306171459.JCFAEPYe-lkp@intel.com> (raw)
tree: https://github.com/dcui/tdx decui/upstream-tip/x86/tdx/v7-wip
head: 2ed5ddebd0892b9aba336de12ecfef74076d1ce9
commit: c95e14c94d53cbb21418b661eb397cee1c67dd24 [7/15] x86/hyperv: Support hypercalls for TDX guests
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20230617/202306171459.JCFAEPYe-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
# https://github.com/dcui/tdx/commit/c95e14c94d53cbb21418b661eb397cee1c67dd24
git remote add dcui-tdx https://github.com/dcui/tdx
git fetch --no-tags dcui-tdx decui/upstream-tip/x86/tdx/v7-wip
git checkout c95e14c94d53cbb21418b661eb397cee1c67dd24
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 olddefconfig
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
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/202306171459.JCFAEPYe-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: vmlinux.o: in function `hv_tdx_hypercall':
>> arch/x86/hyperv/ivm.c:427: undefined reference to `__tdx_hypercall_ret'
vim +427 arch/x86/hyperv/ivm.c
418
419 u64 hv_tdx_hypercall(u64 control, u64 param1, u64 param2)
420 {
421 struct tdx_hypercall_args args = { };
422
423 args.r10 = control;
424 args.rdx = param1;
425 args.r8 = param2;
426
> 427 (void)__tdx_hypercall_ret(&args);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-17 7:00 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=202306171459.JCFAEPYe-lkp@intel.com \
--to=lkp@intel.com \
--cc=decui@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 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.