From: kernel test robot <lkp@intel.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-tdx:kvm-upstream-workaround 435/440] include/linux/kvm_host.h:429:9: error: implicit declaration of function 'perf_event_guest_enter_exit'
Date: Mon, 27 Feb 2023 19:06:10 +0800 [thread overview]
Message-ID: <202302271833.4v9WbSB7-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: 6960696b1b5b8d8074bf2724321ff73782e42e6c
commit: b7377b41927c4fa035228a4eb3fb6151d64bf749 [435/440] perf, KVM: introduce software event on enter/exit to/from guest
config: s390-defconfig (https://download.01.org/0day-ci/archive/20230227/202302271833.4v9WbSB7-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 12.1.0
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/b7377b41927c4fa035228a4eb3fb6151d64bf749
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx kvm-upstream-workaround
git checkout b7377b41927c4fa035228a4eb3fb6151d64bf749
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 prepare
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/202302271833.4v9WbSB7-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/s390/kernel/asm-offsets.c:11:
include/linux/kvm_host.h: In function 'guest_context_enter_irqoff':
>> include/linux/kvm_host.h:429:9: error: implicit declaration of function 'perf_event_guest_enter_exit' [-Werror=implicit-function-declaration]
429 | perf_event_guest_enter_exit(true);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:114: arch/s390/kernel/asm-offsets.s] Error 1
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:1298: prepare0] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:242: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +/perf_event_guest_enter_exit +429 include/linux/kvm_host.h
418
419 /*
420 * Enter guest context and enter an RCU extended quiescent state.
421 *
422 * Between guest_context_enter_irqoff() and guest_context_exit_irqoff() it is
423 * unsafe to use any code which may directly or indirectly use RCU, tracing
424 * (including IRQ flag tracing), or lockdep. All code in this period must be
425 * non-instrumentable.
426 */
427 static __always_inline void guest_context_enter_irqoff(void)
428 {
> 429 perf_event_guest_enter_exit(true);
430 /*
431 * KVM does not hold any references to rcu protected data when it
432 * switches CPU into a guest mode. In fact switching to a guest mode
433 * is very similar to exiting to userspace from rcu point of view. In
434 * addition CPU may stay in a guest mode for quite a long time (up to
435 * one time slice). Lets treat guest mode as quiescent state, just like
436 * we do with user-mode execution.
437 */
438 if (!context_tracking_guest_enter()) {
439 instrumentation_begin();
440 rcu_virt_note_context_switch();
441 instrumentation_end();
442 }
443 }
444
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-02-27 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-01 1:48 [intel-tdx:kvm-upstream-workaround 435/440] include/linux/kvm_host.h:429:9: error: implicit declaration of function 'perf_event_guest_enter_exit' kernel test robot
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=202302271833.4v9WbSB7-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--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 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.