From: kernel test robot <lkp@intel.com>
To: Carsten Stollmaier <stollmc@amazon.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Woodhouse <dwmw@amazon.co.uk>,
Lilit Janpoladyan <lilitj@amazon.de>,
Sebastian Biemueller <sbiemue@amazon.de>
Subject: [dwmw2:gpc-stealtime 1/1] arch/x86/kvm/x86.c:5242:2: error: call to undeclared function 'kvm_gpc_mark_dirty'; ISO C99 and later do not support implicit function declarations
Date: Wed, 04 Feb 2026 09:03:34 +0100 [thread overview]
Message-ID: <202602040904.0eXBWOvu-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/dwmw2/linux gpc-stealtime
head: 34c3f2e56cbf5d6b03946d531e66a91566d90db6
commit: 34c3f2e56cbf5d6b03946d531e66a91566d90db6 [1/1] KVM: x86: Use gfn_to_pfn_cache for record_steal_time
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260204/202602040904.0eXBWOvu-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260204/202602040904.0eXBWOvu-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/202602040904.0eXBWOvu-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kvm/x86.c:5242:2: error: call to undeclared function 'kvm_gpc_mark_dirty'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
5242 | kvm_gpc_mark_dirty(gpc);
| ^
1 error generated.
vim +/kvm_gpc_mark_dirty +5242 arch/x86/kvm/x86.c
5201
5202 static void kvm_steal_time_set_preempted(struct kvm_vcpu *vcpu)
5203 {
5204 struct gfn_to_pfn_cache *gpc = &vcpu->arch.st.cache;
5205 struct kvm_steal_time *st;
5206 static const u8 preempted = KVM_VCPU_PREEMPTED;
5207 unsigned long flags;
5208
5209 /*
5210 * The vCPU can be marked preempted if and only if the VM-Exit was on
5211 * an instruction boundary and will not trigger guest emulation of any
5212 * kind (see vcpu_run). Vendor specific code controls (conservatively)
5213 * when this is true, for example allowing the vCPU to be marked
5214 * preempted if and only if the VM-Exit was due to a host interrupt.
5215 */
5216 if (!vcpu->arch.at_instruction_boundary) {
5217 vcpu->stat.preemption_other++;
5218 return;
5219 }
5220
5221 vcpu->stat.preemption_reported++;
5222 if (!(vcpu->arch.st.msr_val & KVM_MSR_ENABLED))
5223 return;
5224
5225 if (vcpu->arch.st.preempted)
5226 return;
5227
5228 /* This happens on process exit */
5229 if (unlikely(current->mm != vcpu->kvm->mm))
5230 return;
5231
5232 read_lock_irqsave(&gpc->lock, flags);
5233 if (!kvm_gpc_check(gpc, sizeof(*st)))
5234 goto out_unlock_gpc;
5235
5236 st = (struct kvm_steal_time *)gpc->khva;
5237 BUILD_BUG_ON(sizeof(st->preempted) != sizeof(preempted));
5238
5239 st->preempted = preempted;
5240 vcpu->arch.st.preempted = KVM_VCPU_PREEMPTED;
5241
> 5242 kvm_gpc_mark_dirty(gpc);
5243
5244 out_unlock_gpc:
5245 read_unlock_irqrestore(&gpc->lock, flags);
5246 }
5247
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-04 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 8:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-04 8:32 [dwmw2:gpc-stealtime 1/1] arch/x86/kvm/x86.c:5242:2: error: call to undeclared function 'kvm_gpc_mark_dirty'; ISO C99 and later do not support implicit function declarations 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=202602040904.0eXBWOvu-lkp@intel.com \
--to=lkp@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=lilitj@amazon.de \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sbiemue@amazon.de \
--cc=stollmc@amazon.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