From: kbuild test robot <lkp@intel.com>
To: Raghavendra Rao Ananta <rananta@codeaurora.org>
Cc: kbuild-all@01.org, peterz@infradead.org, mingo@redhat.com,
acme@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org, psodagud@codeaurora.org,
tsoni@codeaurora.org, rananta@codeaurora.org
Subject: Re: [PATCH] perf: Add support for creating offline events
Date: Tue, 13 Feb 2018 03:11:22 +0800 [thread overview]
Message-ID: <201802130238.0csUa67V%fengguang.wu@intel.com> (raw)
In-Reply-To: <1518217620-28458-1-git-send-email-rananta@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
Hi Raghavendra,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.15]
[also build test ERROR on next-20180212]
[cannot apply to tip/perf/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Raghavendra-Rao-Ananta/perf-Add-support-for-creating-offline-events/20180213-023250
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel//events/core.c: In function 'perf_event_init_cpu':
>> kernel//events/core.c:11152:2: error: implicit declaration of function 'perf_deferred_install_in_context'; did you mean 'perf_install_in_context'? [-Werror=implicit-function-declaration]
perf_deferred_install_in_context(cpu);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
perf_install_in_context
cc1: some warnings being treated as errors
vim +11152 kernel//events/core.c
11131
11132 int perf_event_init_cpu(unsigned int cpu)
11133 {
11134 struct perf_cpu_context *cpuctx;
11135 struct perf_event_context *ctx;
11136 struct pmu *pmu;
11137
11138 perf_swevent_init_cpu(cpu);
11139
11140 mutex_lock(&pmus_lock);
11141 cpumask_set_cpu(cpu, perf_online_mask);
11142 list_for_each_entry(pmu, &pmus, entry) {
11143 cpuctx = per_cpu_ptr(pmu->pmu_cpu_context, cpu);
11144 ctx = &cpuctx->ctx;
11145
11146 mutex_lock(&ctx->mutex);
11147 cpuctx->online = 1;
11148 mutex_unlock(&ctx->mutex);
11149 }
11150 mutex_unlock(&pmus_lock);
11151
11152 perf_deferred_install_in_context(cpu);
11153
11154 return 0;
11155 }
11156
---
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: 6773 bytes --]
next prev parent reply other threads:[~2018-02-12 19:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 23:07 Raghavendra Rao Ananta
2018-02-12 9:43 ` Jiri Olsa
2018-02-12 17:42 ` Raghavendra Rao Ananta
2018-02-12 21:04 ` Jiri Olsa
2018-02-12 21:21 ` Jiri Olsa
2018-02-12 22:22 ` Raghavendra Rao Ananta
2018-02-13 16:08 ` Jiri Olsa
2018-02-13 18:03 ` Raghavendra Rao Ananta
2018-02-12 9:44 ` Jiri Olsa
2018-02-12 19:11 ` kbuild test robot [this message]
2018-02-13 18:23 ` Peter Zijlstra
2018-02-13 22:17 ` Sodagudi Prasad
2018-02-14 8:32 ` Peter Zijlstra
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=201802130238.0csUa67V%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=psodagud@codeaurora.org \
--cc=rananta@codeaurora.org \
--cc=tsoni@codeaurora.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
Powered by JetHome