From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
David Stevens <stevensd@chromium.org>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: [sean-jc:x86/mmu_follow_pfn 13/28] arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987:18: error: 'struct kvm_follow_pfn' has no member named 'atomic'
Date: Sat, 22 Jun 2024 19:48:36 +0800 [thread overview]
Message-ID: <202406221925.KFeQFUgm-lkp@intel.com> (raw)
tree: https://github.com/sean-jc/linux x86/mmu_follow_pfn
head: 57ff012a34bc3bfac1ebb0724078e8fe47fdb60a
commit: 2e1ef556dc18d78c75fc1ddc11cb770a3de6eb61 [13/28] KVM: mmu: Introduce kvm_follow_pfn()
config: x86_64-randconfig-161-20240622 (https://download.01.org/0day-ci/archive/20240622/202406221925.KFeQFUgm-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240622/202406221925.KFeQFUgm-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/202406221925.KFeQFUgm-lkp@intel.com/
Note: the sean-jc/x86/mmu_follow_pfn HEAD 57ff012a34bc3bfac1ebb0724078e8fe47fdb60a builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
arch/x86/kvm/../../../virt/kvm/kvm_main.c: In function '__gfn_to_pfn_memslot':
>> arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987:18: error: 'struct kvm_follow_pfn' has no member named 'atomic'
2987 | .atomic = atomic,
| ^~~~~~
>> arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987:27: error: 'atomic' undeclared (first use in this function); did you mean 'atomic_t'?
2987 | .atomic = atomic,
| ^~~~~~
| atomic_t
arch/x86/kvm/../../../virt/kvm/kvm_main.c:2987:27: note: each undeclared identifier is reported only once for each function it appears in
vim +2987 arch/x86/kvm/../../../virt/kvm/kvm_main.c
2979
2980 kvm_pfn_t __gfn_to_pfn_memslot(const struct kvm_memory_slot *slot, gfn_t gfn,
2981 bool interruptible, bool no_wait,
2982 bool write_fault, bool *writable)
2983 {
2984 struct kvm_follow_pfn kfp = {
2985 .slot = slot,
2986 .gfn = gfn,
> 2987 .atomic = atomic,
2988 .map_writable = writable,
2989 };
2990
2991 if (write_fault)
2992 kfp.flags |= FOLL_WRITE;
2993 if (no_wait)
2994 kfp.flags |= FOLL_NOWAIT;
2995 if (interruptible)
2996 kfp.flags |= FOLL_INTERRUPTIBLE;
2997
2998 return kvm_follow_pfn(&kfp);
2999 }
3000 EXPORT_SYMBOL_GPL(__gfn_to_pfn_memslot);
3001
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-22 11:48 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=202406221925.KFeQFUgm-lkp@intel.com \
--to=lkp@intel.com \
--cc=mlevitsk@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.com \
--cc=stevensd@chromium.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.