From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [intel-tdx:kvm-upstream-workaround 27/402] vmlinux.o: warning: objtool: kvm_guest_init()+0xba: relocation to !ENDBR: __raw_callee_save___kvm_vcpu_is_preempted()+0x0
Date: Tue, 17 May 2022 04:45:00 +0800 [thread overview]
Message-ID: <202205170436.lsY31f4S-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
TO: Li RongQing <lirongqing@baidu.com>
CC: Isaku Yamahata <isaku.yamahata@intel.com>
CC: Paolo Bonzini <pbonzini@redhat.com>
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: ac4f0c947148ba45f7a99d3e0c1779d299fbb2c1
commit: 7d00d7d179ef40ccdc3ce3f4b52a87a5ff83e0de [27/402] KVM: x86: Support the vCPU preemption check with nopvspin and realtime hint
config: x86_64-randconfig-a001-20220516 (https://download.01.org/0day-ci/archive/20220517/202205170436.lsY31f4S-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 853fa8ee225edf2d0de94b0dcbd31bea916e825e)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel/tdx/commit/7d00d7d179ef40ccdc3ce3f4b52a87a5ff83e0de
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout 7d00d7d179ef40ccdc3ce3f4b52a87a5ff83e0de
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
vmlinux.o: warning: objtool: ibt_selftest()+0xf: sibling call from callable instruction with modified stack frame
>> vmlinux.o: warning: objtool: kvm_guest_init()+0xba: relocation to !ENDBR: __raw_callee_save___kvm_vcpu_is_preempted()+0x0
vmlinux.o: warning: objtool: sync_regs()+0x28: call to memcpy() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret()+0x2a: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_task_stack()+0x14: call to task_stack_page() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_entry_stack()+0x18: call to cpu_entry_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_nmi()+0x117: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: exc_page_fault()+0x3b: call to __kasan_check_read() leaves .noinstr.text section
vmlinux.o: warning: objtool: ibt_selftest()+0x19: return with modified stack frame
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-16 20:45 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=202205170436.lsY31f4S-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
/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