From: kernel test robot <lkp@intel.com>
To: Nam Cao <namcao@linutronix.de>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andreas Hindborg <a.hindborg@kernel.org>,
Alice Ryhl <aliceryhl@google.com>,
Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Nam Cao <namcao@linutronix.de>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH 04/31] KVM: x86: Switch to use hrtimer_setup()
Date: Mon, 28 Oct 2024 21:53:25 +0800 [thread overview]
Message-ID: <202410282113.l2iM0IOZ-lkp@intel.com> (raw)
In-Reply-To: <8774212e6c10c550743219e00738492eb379227c.1729864823.git.namcao@linutronix.de>
Hi Nam,
kernel test robot noticed the following build errors:
[auto build test ERROR on kvm/queue]
[also build test ERROR on tip/sched/core perf-tools-next/perf-tools-next tip/perf/core perf-tools/perf-tools tip/timers/core axboe-block/for-next linus/master v6.12-rc5 next-20241028]
[cannot apply to kvm/linux-next acme/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nam-Cao/KVM-MIPS-Switch-to-use-hrtimer_setup/20241028-154142
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link: https://lore.kernel.org/r/8774212e6c10c550743219e00738492eb379227c.1729864823.git.namcao%40linutronix.de
patch subject: [PATCH 04/31] KVM: x86: Switch to use hrtimer_setup()
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241028/202410282113.l2iM0IOZ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241028/202410282113.l2iM0IOZ-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/202410282113.l2iM0IOZ-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/x86/kvm/lapic.c: In function 'kvm_create_lapic':
>> arch/x86/kvm/lapic.c:2878:9: error: implicit declaration of function 'hrtimer_setup'; did you mean 'timer_setup'? [-Werror=implicit-function-declaration]
2878 | hrtimer_setup(&apic->lapic_timer.timer, apic_timer_fn, CLOCK_MONOTONIC,
| ^~~~~~~~~~~~~
| timer_setup
cc1: some warnings being treated as errors
--
arch/x86/kvm/i8254.c: In function 'kvm_create_pit':
>> arch/x86/kvm/i8254.c:693:9: error: implicit declaration of function 'hrtimer_setup'; did you mean 'timer_setup'? [-Werror=implicit-function-declaration]
693 | hrtimer_setup(&pit_state->timer, pit_timer_fn, CLOCK_MONOTONIC, HRTIMER_MODE_ABS);
| ^~~~~~~~~~~~~
| timer_setup
cc1: some warnings being treated as errors
--
arch/x86/kvm/hyperv.c: In function 'stimer_init':
>> arch/x86/kvm/hyperv.c:955:9: error: implicit declaration of function 'hrtimer_setup'; did you mean 'timer_setup'? [-Werror=implicit-function-declaration]
955 | hrtimer_setup(&stimer->timer, stimer_timer_callback, CLOCK_MONOTONIC, HRTIMER_MODE_ABS);
| ^~~~~~~~~~~~~
| timer_setup
cc1: some warnings being treated as errors
--
arch/x86/kvm/vmx/nested.c: In function 'enter_vmx_operation':
>> arch/x86/kvm/vmx/nested.c:5278:9: error: implicit declaration of function 'hrtimer_setup'; did you mean 'timer_setup'? [-Werror=implicit-function-declaration]
5278 | hrtimer_setup(&vmx->nested.preemption_timer, vmx_preemption_timer_fn, CLOCK_MONOTONIC,
| ^~~~~~~~~~~~~
| timer_setup
cc1: some warnings being treated as errors
vim +2878 arch/x86/kvm/lapic.c
2847
2848 int kvm_create_lapic(struct kvm_vcpu *vcpu)
2849 {
2850 struct kvm_lapic *apic;
2851
2852 ASSERT(vcpu != NULL);
2853
2854 if (!irqchip_in_kernel(vcpu->kvm)) {
2855 static_branch_inc(&kvm_has_noapic_vcpu);
2856 return 0;
2857 }
2858
2859 apic = kzalloc(sizeof(*apic), GFP_KERNEL_ACCOUNT);
2860 if (!apic)
2861 goto nomem;
2862
2863 vcpu->arch.apic = apic;
2864
2865 if (kvm_x86_ops.alloc_apic_backing_page)
2866 apic->regs = kvm_x86_call(alloc_apic_backing_page)(vcpu);
2867 else
2868 apic->regs = (void *)get_zeroed_page(GFP_KERNEL_ACCOUNT);
2869 if (!apic->regs) {
2870 printk(KERN_ERR "malloc apic regs error for vcpu %x\n",
2871 vcpu->vcpu_id);
2872 goto nomem_free_apic;
2873 }
2874 apic->vcpu = vcpu;
2875
2876 apic->nr_lvt_entries = kvm_apic_calc_nr_lvt_entries(vcpu);
2877
> 2878 hrtimer_setup(&apic->lapic_timer.timer, apic_timer_fn, CLOCK_MONOTONIC,
2879 HRTIMER_MODE_ABS_HARD);
2880 if (lapic_timer_advance)
2881 apic->lapic_timer.timer_advance_ns = LAPIC_TIMER_ADVANCE_NS_INIT;
2882
2883 /*
2884 * Stuff the APIC ENABLE bit in lieu of temporarily incrementing
2885 * apic_hw_disabled; the full RESET value is set by kvm_lapic_reset().
2886 */
2887 vcpu->arch.apic_base = MSR_IA32_APICBASE_ENABLE;
2888 static_branch_inc(&apic_sw_disabled.key); /* sw disabled at reset */
2889 kvm_iodevice_init(&apic->dev, &apic_mmio_ops);
2890
2891 /*
2892 * Defer evaluating inhibits until the vCPU is first run, as this vCPU
2893 * will not get notified of any changes until this vCPU is visible to
2894 * other vCPUs (marked online and added to the set of vCPUs).
2895 *
2896 * Opportunistically mark APICv active as VMX in particularly is highly
2897 * unlikely to have inhibits. Ignore the current per-VM APICv state so
2898 * that vCPU creation is guaranteed to run with a deterministic value,
2899 * the request will ensure the vCPU gets the correct state before VM-Entry.
2900 */
2901 if (enable_apicv) {
2902 apic->apicv_active = true;
2903 kvm_make_request(KVM_REQ_APICV_UPDATE, vcpu);
2904 }
2905
2906 return 0;
2907 nomem_free_apic:
2908 kfree(apic);
2909 vcpu->arch.apic = NULL;
2910 nomem:
2911 return -ENOMEM;
2912 }
2913
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-28 13:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 7:31 [PATCH 00/31] hrtimers: Switch to new hrtimer interface functions (2/5) Nam Cao
2024-10-28 7:31 ` [PATCH 01/31] KVM: MIPS: Switch to use hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 02/31] KVM: PPC: " Nam Cao
2024-10-28 7:31 ` [PATCH 03/31] KVM: s390: " Nam Cao
2024-10-28 7:31 ` [PATCH 04/31] KVM: x86: " Nam Cao
2024-10-28 13:53 ` kernel test robot [this message]
2024-10-28 19:17 ` kernel test robot
2024-10-28 7:31 ` [PATCH 05/31] KVM: arm64: " Nam Cao
2024-10-28 10:56 ` Marc Zyngier
2024-10-28 7:31 ` [PATCH 06/31] LoongArch: KVM: " Nam Cao
2024-10-28 7:31 ` [PATCH 07/31] riscv: kvm: " Nam Cao
2024-10-28 7:31 ` [PATCH 08/31] ARM: imx: " Nam Cao
2024-10-28 7:31 ` [PATCH 09/31] ARM: 8611/1: l2x0: " Nam Cao
2024-10-28 7:31 ` [PATCH 10/31] powerpc/watchdog: " Nam Cao
2024-10-28 7:31 ` [PATCH 11/31] perf/x86: " Nam Cao
2024-10-28 7:31 ` [PATCH 12/31] s390/ap_bus: " Nam Cao
2024-10-28 7:31 ` [PATCH 13/31] sched: " Nam Cao
2024-10-28 12:51 ` kernel test robot
2024-10-28 7:31 ` [PATCH 14/31] rcu: " Nam Cao
2024-10-28 13:52 ` Paul E. McKenney
2024-10-28 7:31 ` [PATCH 15/31] lib: test_objpool: " Nam Cao
2024-10-28 7:31 ` [PATCH 16/31] io_uring/timeout: " Nam Cao
2025-05-02 8:50 ` Pavel Begunkov
2024-10-28 7:31 ` [PATCH 17/31] fork: " Nam Cao
2024-10-28 7:31 ` [PATCH 18/31] perf: " Nam Cao
2024-10-28 7:31 ` [PATCH 19/31] timerfd: " Nam Cao
2024-10-28 7:31 ` [PATCH 20/31] time: Switch to hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 21/31] bpf: Switch to use hrtimer_setup() Nam Cao
2024-10-28 7:31 ` [PATCH 22/31] ubifs: " Nam Cao
2024-10-28 7:31 ` [PATCH 23/31] watchdog: " Nam Cao
2024-10-28 7:31 ` [PATCH 24/31] tracing/osnoise: " Nam Cao
2024-10-28 7:52 ` Steven Rostedt
2024-10-28 7:31 ` [PATCH 25/31] block, bfq: " Nam Cao
2024-10-28 7:31 ` [PATCH 26/31] ata: pata_octeon_cf: " Nam Cao
2024-10-29 23:41 ` Damien Le Moal
2024-10-28 7:32 ` [PATCH 27/31] blk_iocost: " Nam Cao
2024-10-28 7:32 ` [PATCH 28/31] PM: runtime: " Nam Cao
2024-10-28 11:43 ` Rafael J. Wysocki
2024-10-28 7:32 ` [PATCH 29/31] PM / devfreq: rockchip-dfi: " Nam Cao
2024-12-08 12:39 ` Chanwoo Choi
2024-10-28 7:32 ` [PATCH 30/31] null_blk: " Nam Cao
2024-10-28 7:32 ` [PATCH 31/31] hwrng: timeriomem: " Nam Cao
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=202410282113.l2iM0IOZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
/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.