[sashal-linux-stable:queue-5.10 58/74] arch/x86/kvm/mmu/mmu_internal.h:87:20: error: 'struct kvm_x86_ops' has no member named 'cpu_dirty_log_size'

[kernel test robot <lkp@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 3489 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-5.10
head:   9ced6633127bd25a94939777d9ecda54800859fc
commit: 2022a67e630a25e8274ad36e0437d8230d8d716d [58/74] KVM: x86/mmu: Set SPTE_AD_WRPROT_ONLY_MASK if and only if PML is enabled
config: x86_64-randconfig-s021-20210318 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-277-gc089cd2d-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git/commit/?id=2022a67e630a25e8274ad36e0437d8230d8d716d
        git remote add sashal-linux-stable https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
        git fetch --no-tags sashal-linux-stable queue-5.10
        git checkout 2022a67e630a25e8274ad36e0437d8230d8d716d
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from arch/x86/kvm/mmu/mmu.c:21:
   arch/x86/kvm/mmu/mmu_internal.h: In function 'kvm_vcpu_ad_need_write_protect':
>> arch/x86/kvm/mmu/mmu_internal.h:87:20: error: 'struct kvm_x86_ops' has no member named 'cpu_dirty_log_size'
      87 |         kvm_x86_ops.cpu_dirty_log_size;
         |                    ^
--
   In file included from arch/x86/kvm/mmu/spte.c:14:
   arch/x86/kvm/mmu/mmu_internal.h: In function 'kvm_vcpu_ad_need_write_protect':
>> arch/x86/kvm/mmu/mmu_internal.h:87:20: error: 'struct kvm_x86_ops' has no member named 'cpu_dirty_log_size'
      87 |         kvm_x86_ops.cpu_dirty_log_size;
         |                    ^
   arch/x86/kvm/mmu/mmu_internal.h:88:1: error: control reaches end of non-void function [-Werror=return-type]
      88 | }
         | ^
   cc1: some warnings being treated as errors
--
   In file included from arch/x86/kvm/mmu/tdp_iter.c:3:
   arch/x86/kvm/mmu/mmu_internal.h: In function 'kvm_vcpu_ad_need_write_protect':
>> arch/x86/kvm/mmu/mmu_internal.h:87:20: error: 'struct kvm_x86_ops' has no member named 'cpu_dirty_log_size'
      87 |         kvm_x86_ops.cpu_dirty_log_size;
         |                    ^
   In file included from arch/x86/kvm/mmu/tdp_iter.c:4:
   arch/x86/kvm/mmu/tdp_iter.h: At top level:
   arch/x86/kvm/mmu/tdp_iter.h:8:10: fatal error: mmu.h: No such file or directory
       8 | #include "mmu.h"
         |          ^~~~~~~
   compilation terminated.


vim +87 arch/x86/kvm/mmu/mmu_internal.h

    75	
    76	static inline bool kvm_vcpu_ad_need_write_protect(struct kvm_vcpu *vcpu)
    77	{
    78		/*
    79		 * When using the EPT page-modification log, the GPAs in the CPU dirty
    80		 * log would come from L2 rather than L1.  Therefore, we need to rely
    81		 * on write protection to record dirty pages, which bypasses PML, since
    82		 * writes now result in a vmexit.  Note, the check on CPU dirty logging
    83		 * being enabled is mandatory as the bits used to denote WP-only SPTEs
    84		 * are reserved for NPT w/ PAE (32-bit KVM).
    85		 */
    86		return vcpu->arch.mmu == &vcpu->arch.guest_mmu &&
  > 87		       kvm_x86_ops.cpu_dirty_log_size;
    88	}
    89	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35938 bytes --]