From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:kvm-arm64/vcpu-xarray 2/2] arch/x86/kvm/vmx/posted_intr.c:261:32: error: 'struct kvm' has no member named 'vcpus'
Date: Sat, 2 Jan 2021 16:44:14 +0800 [thread overview]
Message-ID: <202101021608.WQ70GyoX-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3320 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git kvm-arm64/vcpu-xarray
head: 8069e9ac6315f0b552565c8d96f32cc6d77d0456
commit: 8069e9ac6315f0b552565c8d96f32cc6d77d0456 [2/2] KVM: Convert the kvm->vcpus array to a xarray
config: x86_64-rhel (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?id=8069e9ac6315f0b552565c8d96f32cc6d77d0456
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms kvm-arm64/vcpu-xarray
git checkout 8069e9ac6315f0b552565c8d96f32cc6d77d0456
# save the attached .config to linux build tree
make W=1 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 >>):
arch/x86/kvm/vmx/posted_intr.c: In function 'pi_update_irte':
>> arch/x86/kvm/vmx/posted_intr.c:261:32: error: 'struct kvm' has no member named 'vcpus'
261 | !kvm_vcpu_apicv_active(kvm->vcpus[0]))
| ^~
vim +261 arch/x86/kvm/vmx/posted_intr.c
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 238
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 239
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 240 /*
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 241 * pi_update_irte - set IRTE for Posted-Interrupts
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 242 *
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 243 * @kvm: kvm
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 244 * @host_irq: host irq of the interrupt
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 245 * @guest_irq: gsi of the interrupt
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 246 * @set: set or unset PI
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 247 * returns 0 on success, < 0 on failure
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 248 */
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 249 int pi_update_irte(struct kvm *kvm, unsigned int host_irq, uint32_t guest_irq,
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 250 bool set)
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 251 {
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 252 struct kvm_kernel_irq_routing_entry *e;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 253 struct kvm_irq_routing_table *irq_rt;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 254 struct kvm_lapic_irq irq;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 255 struct kvm_vcpu *vcpu;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 256 struct vcpu_data vcpu_info;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 257 int idx, ret = 0;
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 258
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 259 if (!kvm_arch_has_assigned_device(kvm) ||
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 260 !irq_remapping_cap(IRQ_POSTING_CAP) ||
8888cdd0996c2d5 Xiaoyao Li 2020-09-23 @261 !kvm_vcpu_apicv_active(kvm->vcpus[0]))
:::::: The code at line 261 was first introduced by commit
:::::: 8888cdd0996c2d51cd417f9a60a282c034f3fa28 KVM: VMX: Extract posted interrupt support to separate files
:::::: TO: Xiaoyao Li <xiaoyao.li@intel.com>
:::::: CC: Paolo Bonzini <pbonzini@redhat.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45918 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-01-02 8: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=202101021608.WQ70GyoX-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).