llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Isaku Yamahata <isaku.yamahata@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [intel-tdx:kvm-upstream-next 70/252] arch/x86/kvm/vmx/main.c:83:17: error: no member named 'flush_remote_tlbs' in 'struct kvm_x86_ops'
Date: Wed, 24 Jan 2024 13:54:41 +0800	[thread overview]
Message-ID: <202401241306.xcL02JqR-lkp@intel.com> (raw)

tree:   https://github.com/intel/tdx.git kvm-upstream-next
head:   cd5f3a9ef935bc249a18a3c6607ae2128c1ced06
commit: a47c5a9442130f45fc09c1d4ae0e4352054be636 [70/252] KVM: TDX: TDP MMU TDX support
config: x86_64-buildonly-randconfig-001-20240124 (https://download.01.org/0day-ci/archive/20240124/202401241306.xcL02JqR-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240124/202401241306.xcL02JqR-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/202401241306.xcL02JqR-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/x86/kvm/vmx/main.c:83:17: error: no member named 'flush_remote_tlbs' in 'struct kvm_x86_ops'
      83 |         if (vt_x86_ops.flush_remote_tlbs ||
         |             ~~~~~~~~~~ ^
>> arch/x86/kvm/vmx/main.c:84:17: error: no member named 'flush_remote_tlbs_range' in 'struct kvm_x86_ops'
      84 |             vt_x86_ops.flush_remote_tlbs_range) {
         |             ~~~~~~~~~~ ^
   arch/x86/kvm/vmx/main.c:92:14: error: no member named 'flush_remote_tlbs' in 'struct kvm_x86_ops'
      92 |                 vt_x86_ops.flush_remote_tlbs = vt_flush_remote_tlbs;
         |                 ~~~~~~~~~~ ^
   3 errors generated.


vim +83 arch/x86/kvm/vmx/main.c

    50	
    51	static __init int vt_hardware_setup(void)
    52	{
    53		int ret;
    54	
    55		ret = vmx_hardware_setup();
    56		if (ret)
    57			return ret;
    58	
    59		/*
    60		 * As kvm_mmu_set_ept_masks() updates enable_mmio_caching, call it
    61		 * before checking enable_mmio_caching.
    62		 */
    63		if (enable_ept)
    64			kvm_mmu_set_ept_masks(enable_ept_ad_bits,
    65					      cpu_has_vmx_ept_execute_only());
    66		/* TDX requires KVM TDP MMU. */
    67		if (enable_tdx && !tdp_enabled) {
    68			enable_tdx = false;
    69			pr_warn_ratelimited("TDX requires TDP MMU.  Please enable TDP MMU for TDX.\n");
    70		}
    71	
    72		/* TDX requires MMIO caching. */
    73		if (enable_tdx && !enable_mmio_caching) {
    74			enable_tdx = false;
    75			pr_warn_ratelimited("TDX requires mmio caching.  Please enable mmio caching for TDX.\n");
    76		}
    77	
    78		/*
    79		 * TDX KVM overrides flush_remote_tlbs method and assumes
    80		 * flush_remote_tlbs_range = NULL that falls back to
    81		 * flush_remote_tlbs.  Disable TDX if there are conflicts.
    82		 */
  > 83		if (vt_x86_ops.flush_remote_tlbs ||
  > 84		    vt_x86_ops.flush_remote_tlbs_range) {
    85			enable_tdx = false;
    86			pr_warn_ratelimited("TDX requires baremetal. Not Supported on VMM guest.\n");
    87		}
    88	
    89		enable_tdx = enable_tdx && !tdx_hardware_setup(&vt_x86_ops);
    90	
    91		if (enable_tdx)
    92			vt_x86_ops.flush_remote_tlbs = vt_flush_remote_tlbs;
    93	
    94		return 0;
    95	}
    96	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-01-24  5:54 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=202401241306.xcL02JqR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=isaku.yamahata@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;
as well as URLs for NNTP newsgroup(s).