From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [jpoimboe:static-key-noinstr 3/3] vmlinux.o: warning: objtool: vmx_update_host_rsp+0x27: __kvm_is_using_evmcs: non-RO static key usage in noinstr
Date: Mon, 16 Dec 2024 08:20:03 +0800 [thread overview]
Message-ID: <202412160853.H0ep2D3A-lkp@intel.com> (raw)
TO: Josh Poimboeuf <jpoimboe@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git static-key-noinstr
head: 59b1dc64303468b5c81a6197d9865b6e08046c94
commit: 59b1dc64303468b5c81a6197d9865b6e08046c94 [3/3] objtool: Add noinstr validation for static branches/calls
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20241216/202412160853.H0ep2D3A-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241216/202412160853.H0ep2D3A-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/202412160853.H0ep2D3A-lkp@intel.com/
All warnings (new ones prefixed by >>):
vmlinux.o: warning: objtool: nvmet_ctrl_state_show() falls through to next function __cfi_nvmet_ctrl_host_traddr_open()
vmlinux.o: warning: objtool: tw28_set_ctrl_val() falls through to next function __cfi_tw28_get_ctrl_val()
>> vmlinux.o: warning: objtool: vmx_update_host_rsp+0x27: __kvm_is_using_evmcs: non-RO static key usage in noinstr
>> vmlinux.o: warning: objtool: vmx_vcpu_enter_exit+0x18a: __kvm_is_using_evmcs: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: vmx_l1d_flush+0x7: vmx_l1d_flush_cond: non-RO static key usage in noinstr
>> vmlinux.o: warning: objtool: exc_nmi+0x2b6: microcode_nmi_handler_enable: non-RO static key usage in noinstr
>> vmlinux.o: warning: objtool: fred_exc_nmi+0x89: microcode_nmi_handler_enable: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: sched_clock_noinstr+0x4: pv_sched_clock: non-RO static call usage in noinstr
>> vmlinux.o: warning: objtool: pv_native_safe_halt+0x4: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: local_clock_noinstr+0x5: __sched_clock_stable: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: arch_cpu_idle+0x4: x86_idle: non-RO static call usage in noinstr
vmlinux.o: warning: objtool: mwait_idle+0x45: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: acpi_processor_ffh_cstate_enter+0xc0: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: intel_idle+0x62: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: intel_idle_s2idle+0x73: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: intel_idle_xstate+0x6b: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: intel_idle_ibrs+0x9c: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: intel_idle_irq+0x62: mds_idle_clear: non-RO static key usage in noinstr
vmlinux.o: warning: objtool: acpi_idle_do_entry+0x9: perf_lopwr_cb: non-RO static call usage in noinstr
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-16 0:20 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=202412160853.H0ep2D3A-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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