From: kernel test robot <lkp@intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
xiaoyao.li@intel.com, farrah.chen@intel.com
Subject: Re: [PATCH v2] KVM: x86: Don't read guest CR3 when doing async pf while the MMU is direct
Date: Sat, 13 Dec 2025 07:38:13 +0800 [thread overview]
Message-ID: <202512130717.aHH8rXSC-lkp@intel.com> (raw)
In-Reply-To: <20251212135051.2155280-1-xiaoyao.li@intel.com>
Hi Xiaoyao,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 7d0a66e4bb9081d75c82ec4957c50034cb0ea449]
url: https://github.com/intel-lab-lkp/linux/commits/Xiaoyao-Li/KVM-x86-Don-t-read-guest-CR3-when-doing-async-pf-while-the-MMU-is-direct/20251212-220612
base: 7d0a66e4bb9081d75c82ec4957c50034cb0ea449
patch link: https://lore.kernel.org/r/20251212135051.2155280-1-xiaoyao.li%40intel.com
patch subject: [PATCH v2] KVM: x86: Don't read guest CR3 when doing async pf while the MMU is direct
config: i386-buildonly-randconfig-002-20251213 (https://download.01.org/0day-ci/archive/20251213/202512130717.aHH8rXSC-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251213/202512130717.aHH8rXSC-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/202512130717.aHH8rXSC-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/linux/kvm_host.h:43,
from arch/x86/kvm/irq.h:15,
from arch/x86/kvm/mmu/mmu.c:19:
arch/x86/kvm/mmu/mmu.c: In function 'kvm_arch_setup_async_pf':
>> include/linux/kvm_types.h:54:25: warning: conversion from 'long long unsigned int' to 'long unsigned int' changes value from '18446744073709551615' to '4294967295' [-Woverflow]
54 | #define INVALID_GPA (~(gpa_t)0)
| ^
arch/x86/kvm/mmu/mmu.c:4525:28: note: in expansion of macro 'INVALID_GPA'
4525 | arch.cr3 = INVALID_GPA;
| ^~~~~~~~~~~
vim +54 include/linux/kvm_types.h
d77a39d982431e drivers/kvm/types.h Hollis Blanchard 2007-12-03 53
cecafc0a830f7e include/linux/kvm_types.h Yu Zhang 2023-01-05 @54 #define INVALID_GPA (~(gpa_t)0)
8564d6372a7d8a include/linux/kvm_types.h Steven Price 2019-10-21 55
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-12-12 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:50 [PATCH v2] KVM: x86: Don't read guest CR3 when doing async pf while the MMU is direct Xiaoyao Li
2025-12-12 23:38 ` kernel test robot [this message]
2025-12-13 1:01 ` Sean Christopherson
2025-12-15 2:30 ` Xiaoyao Li
2025-12-15 20:51 ` Sean Christopherson
2025-12-13 1:38 ` kernel test robot
2026-01-12 17:38 ` Sean Christopherson
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=202512130717.aHH8rXSC-lkp@intel.com \
--to=lkp@intel.com \
--cc=farrah.chen@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=xiaoyao.li@intel.com \
/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