tree: https://github.com/intel/tdx.git kvm-upstream-workaround head: c2b43d6ee32b2f2de54395e7b2d7ba9bfa727608 commit: e11dbdbae913817716494fb41eb22aa88e1464e0 [296/418] KVM: Add KVM_EXIT_MEMORY_FAULT exit reproduce: make htmldocs If you fix the issue, kindly add following tag where applicable Reported-by: kernel test robot <lkp@xxxxxxxxx> All warnings (new ones prefixed by >>): >> Documentation/virt/kvm/api.rst:6679: WARNING: Definition list ends without a blank line; unexpected unindent. vim +6679 Documentation/virt/kvm/api.rst 6667 6668 }; 6669 6670 :: 6671 /* KVM_EXIT_MEMORY_FAULT */ 6672 struct { 6673 #define KVM_MEMORY_EXIT_FLAG_PRIVATE (1 << 0) 6674 __u32 flags; 6675 __u32 padding; 6676 __u64 gpa; 6677 __u64 size; 6678 } memory; > 6679 If exit reason is KVM_EXIT_MEMORY_FAULT then it indicates that the VCPU has 6680 encountered a memory error which is not handled by KVM kernel module and 6681 userspace may choose to handle it. The 'flags' field indicates the memory 6682 properties of the exit. 6683 6684 - KVM_MEMORY_EXIT_FLAG_PRIVATE - indicates the memory error is caused by 6685 private memory access when the bit is set otherwise the memory error is 6686 caused by shared memory access when the bit is clear. 6687 -- 0-DAY CI Kernel Test Service https://01.org/lkp
