From: kernel test robot <lkp@intel.com>
To: Tianyu Lan <ltykernel@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC Patch v2 2/4] drivers/hv: Allow vmbus message synic interrupt injected from Hyper-V
Date: Sat, 14 Jun 2025 22:15:17 +0800 [thread overview]
Message-ID: <202506142114.LRNCd3ev-lkp@intel.com> (raw)
In-Reply-To: <20250613110829.122371-3-ltykernel@gmail.com>
Hi Tianyu,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/x86/core]
[also build test ERROR on linus/master v6.16-rc1 next-20250613]
[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/Tianyu-Lan/x86-Hyper-V-Not-use-hv-apic-driver-when-Secure-AVIC-is-available/20250613-191041
base: tip/x86/core
patch link: https://lore.kernel.org/r/20250613110829.122371-3-ltykernel%40gmail.com
patch subject: [RFC Patch v2 2/4] drivers/hv: Allow vmbus message synic interrupt injected from Hyper-V
config: arm64-randconfig-002-20250614 (https://download.01.org/0day-ci/archive/20250614/202506142114.LRNCd3ev-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250614/202506142114.LRNCd3ev-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/202506142114.LRNCd3ev-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/hv/hv.c:23:10: fatal error: asm/apic.h: No such file or directory
23 | #include <asm/apic.h>
| ^~~~~~~~~~~~
compilation terminated.
vim +23 drivers/hv/hv.c
10
11 #include <linux/io.h>
12 #include <linux/kernel.h>
13 #include <linux/mm.h>
14 #include <linux/slab.h>
15 #include <linux/vmalloc.h>
16 #include <linux/hyperv.h>
17 #include <linux/random.h>
18 #include <linux/clockchips.h>
19 #include <linux/delay.h>
20 #include <linux/interrupt.h>
21 #include <clocksource/hyperv_timer.h>
22 #include <asm/mshyperv.h>
> 23 #include <asm/apic.h>
24 #include <linux/set_memory.h>
25 #include "hyperv_vmbus.h"
26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-14 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:08 [RFC Patch v2 0/4] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform Tianyu Lan
2025-06-13 11:08 ` [RFC Patch v2 1/4] x86/Hyper-V: Not use hv apic driver when Secure AVIC is available Tianyu Lan
2025-06-20 2:17 ` Michael Kelley
2025-06-13 11:08 ` [RFC Patch v2 2/4] drivers/hv: Allow vmbus message synic interrupt injected from Hyper-V Tianyu Lan
2025-06-14 14:15 ` kernel test robot [this message]
2025-06-20 2:17 ` Michael Kelley
2025-06-13 11:08 ` [RFC Patch v2 3/4] x86/Hyper-V: Not use auto-eoi when Secure AVIC is available Tianyu Lan
2025-06-14 13:32 ` kernel test robot
2025-06-20 2:17 ` Michael Kelley
2025-06-13 11:08 ` [RFC Patch v2 4/4] x86/Hyper-V: Allow Hyper-V to inject Hyper-V vectors Tianyu Lan
2025-06-20 2:18 ` Michael Kelley
2025-06-20 2:17 ` [RFC Patch v2 0/4] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform Michael Kelley
2025-06-20 15:05 ` Tianyu Lan
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=202506142114.LRNCd3ev-lkp@intel.com \
--to=lkp@intel.com \
--cc=ltykernel@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.