From: kbuild test robot <lkp@intel.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: kbuild-all@01.org, Michael Kelley <mikelley@microsoft.com>,
Lan Tianyu <Tianyu.Lan@microsoft.com>,
Joerg Roedel <jroedel@suse.de>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Sasha Levin <sashal@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] x86/hyperv: make vapic support x2apic mode
Date: Tue, 1 Oct 2019 07:04:48 +0800 [thread overview]
Message-ID: <201910010746.YRiyyhdP%lkp@intel.com> (raw)
In-Reply-To: <20190930173332.13655-1-rkagan@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 2681 bytes --]
Hi Roman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/x86/core]
[cannot apply to v5.4-rc1 next-20190930]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Roman-Kagan/x86-hyperv-make-vapic-support-x2apic-mode/20191001-044238
config: x86_64-randconfig-s0-201939 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86//hyperv/hv_apic.c: In function 'hv_x2apic_read':
>> arch/x86//hyperv/hv_apic.c:91:10: error: implicit declaration of function 'native_apic_msr_read' [-Werror=implicit-function-declaration]
return native_apic_msr_read(reg);
^
arch/x86//hyperv/hv_apic.c: In function 'hv_x2apic_write':
>> arch/x86//hyperv/hv_apic.c:119:3: error: implicit declaration of function 'native_apic_msr_write' [-Werror=implicit-function-declaration]
native_apic_msr_write(reg, val);
^
cc1: some warnings being treated as errors
vim +/native_apic_msr_read +91 arch/x86//hyperv/hv_apic.c
77
78 static u32 hv_x2apic_read(u32 reg)
79 {
80 u32 reg_val, hi;
81
82 switch (reg) {
83 case APIC_EOI:
84 rdmsr(HV_X64_MSR_EOI, reg_val, hi);
85 return reg_val;
86 case APIC_TASKPRI:
87 rdmsr(HV_X64_MSR_TPR, reg_val, hi);
88 return reg_val;
89
90 default:
> 91 return native_apic_msr_read(reg);
92 }
93 }
94
95 static void hv_apic_write(u32 reg, u32 val)
96 {
97 switch (reg) {
98 case APIC_EOI:
99 wrmsr(HV_X64_MSR_EOI, val, 0);
100 break;
101 case APIC_TASKPRI:
102 wrmsr(HV_X64_MSR_TPR, val, 0);
103 break;
104 default:
105 native_apic_mem_write(reg, val);
106 }
107 }
108
109 static void hv_x2apic_write(u32 reg, u32 val)
110 {
111 switch (reg) {
112 case APIC_EOI:
113 wrmsr(HV_X64_MSR_EOI, val, 0);
114 break;
115 case APIC_TASKPRI:
116 wrmsr(HV_X64_MSR_TPR, val, 0);
117 break;
118 default:
> 119 native_apic_msr_write(reg, val);
120 }
121 }
122
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30710 bytes --]
prev parent reply other threads:[~2019-09-30 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 17:33 [PATCH] x86/hyperv: make vapic support x2apic mode Roman Kagan
2019-09-30 22:44 ` kbuild test robot
2019-10-01 9:18 ` Roman Kagan
2019-09-30 23:04 ` kbuild test robot [this message]
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=201910010746.YRiyyhdP%lkp@intel.com \
--to=lkp@intel.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=bp@alien8.de \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jroedel@suse.de \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@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).