From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] x86: Add trace points to (nearly) all vectors
Date: Sat, 02 Nov 2019 09:24:50 +0800 [thread overview]
Message-ID: <201911020947.N041g9eA%lkp@intel.com> (raw)
In-Reply-To: <20191030195619.22244-1-andi@firstfloor.org>
[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]
Hi Andi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v5.4-rc5 next-20191031]
[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/Andi-Kleen/x86-Add-trace-points-to-nearly-all-vectors/20191102-063457
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a5b576bfb3ba85d3e356f9900dce1428d4760582
config: i386-randconfig-b001-201943 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
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//kernel/kvm.c: In function 'do_async_page_fault':
>> arch/x86//kernel/kvm.c:250:2: error: implicit declaration of function 'trace_async_page_fault_entry'; did you mean 'do_async_page_fault'? [-Werror=implicit-function-declaration]
trace_async_page_fault_entry(0);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
do_async_page_fault
>> arch/x86//kernel/kvm.c:269:2: error: implicit declaration of function 'trace_async_page_fault_exit'; did you mean 'do_async_page_fault'? [-Werror=implicit-function-declaration]
trace_async_page_fault_exit(0);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
do_async_page_fault
cc1: some warnings being treated as errors
vim +250 arch/x86//kernel/kvm.c
244
245 dotraplinkage void
246 do_async_page_fault(struct pt_regs *regs, unsigned long error_code, unsigned long address)
247 {
248 enum ctx_state prev_state;
249
> 250 trace_async_page_fault_entry(0);
251
252 switch (kvm_read_and_reset_pf_reason()) {
253 default:
254 do_page_fault(regs, error_code, address);
255 break;
256 case KVM_PV_REASON_PAGE_NOT_PRESENT:
257 /* page is swapped out by the host. */
258 prev_state = exception_enter();
259 kvm_async_pf_task_wait((u32)address, !user_mode(regs));
260 exception_exit(prev_state);
261 break;
262 case KVM_PV_REASON_PAGE_READY:
263 rcu_irq_enter();
264 kvm_async_pf_task_wake((u32)address);
265 rcu_irq_exit();
266 break;
267 }
268
> 269 trace_async_page_fault_exit(0);
270 }
271 NOKPROBE_SYMBOL(do_async_page_fault);
272
---
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: 32849 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: kbuild-all@lists.01.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH v3] x86: Add trace points to (nearly) all vectors
Date: Sat, 2 Nov 2019 09:24:50 +0800 [thread overview]
Message-ID: <201911020947.N041g9eA%lkp@intel.com> (raw)
In-Reply-To: <20191030195619.22244-1-andi@firstfloor.org>
[-- Attachment #1: Type: text/plain, Size: 2694 bytes --]
Hi Andi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tip/auto-latest]
[also build test ERROR on v5.4-rc5 next-20191031]
[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/Andi-Kleen/x86-Add-trace-points-to-nearly-all-vectors/20191102-063457
base: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a5b576bfb3ba85d3e356f9900dce1428d4760582
config: i386-randconfig-b001-201943 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
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//kernel/kvm.c: In function 'do_async_page_fault':
>> arch/x86//kernel/kvm.c:250:2: error: implicit declaration of function 'trace_async_page_fault_entry'; did you mean 'do_async_page_fault'? [-Werror=implicit-function-declaration]
trace_async_page_fault_entry(0);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
do_async_page_fault
>> arch/x86//kernel/kvm.c:269:2: error: implicit declaration of function 'trace_async_page_fault_exit'; did you mean 'do_async_page_fault'? [-Werror=implicit-function-declaration]
trace_async_page_fault_exit(0);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
do_async_page_fault
cc1: some warnings being treated as errors
vim +250 arch/x86//kernel/kvm.c
244
245 dotraplinkage void
246 do_async_page_fault(struct pt_regs *regs, unsigned long error_code, unsigned long address)
247 {
248 enum ctx_state prev_state;
249
> 250 trace_async_page_fault_entry(0);
251
252 switch (kvm_read_and_reset_pf_reason()) {
253 default:
254 do_page_fault(regs, error_code, address);
255 break;
256 case KVM_PV_REASON_PAGE_NOT_PRESENT:
257 /* page is swapped out by the host. */
258 prev_state = exception_enter();
259 kvm_async_pf_task_wait((u32)address, !user_mode(regs));
260 exception_exit(prev_state);
261 break;
262 case KVM_PV_REASON_PAGE_READY:
263 rcu_irq_enter();
264 kvm_async_pf_task_wake((u32)address);
265 rcu_irq_exit();
266 break;
267 }
268
> 269 trace_async_page_fault_exit(0);
270 }
271 NOKPROBE_SYMBOL(do_async_page_fault);
272
---
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: 32849 bytes --]
next prev parent reply other threads:[~2019-11-02 1:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 19:56 [PATCH v3] x86: Add trace points to (nearly) all vectors Andi Kleen
2019-11-02 0:47 ` kbuild test robot
2019-11-02 0:47 ` kbuild test robot
2019-11-05 1:46 ` Andi Kleen
2019-11-05 1:46 ` Andi Kleen
2019-11-07 1:51 ` Rong Chen
2019-11-07 1:51 ` [kbuild-all] " Rong Chen
2019-11-02 1:24 ` kbuild test robot [this message]
2019-11-02 1:24 ` kbuild test robot
2019-11-05 1:44 ` Andi Kleen
2019-11-05 1:44 ` Andi Kleen
2019-11-05 16:55 ` Andi Kleen
2019-11-05 16:55 ` Andi Kleen
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=201911020947.N041g9eA%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.