From: kbuild test robot <lkp@intel.com>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
"x86@kernel.org" <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, Kan Liang <kan.liang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@suse.de>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
Paul Turner <pjt@google.com>,
Stephane Eranian <eranian@google.com>,
David Carrillo-Cisneros <davidcc@google.com>
Subject: Re: [PATCH] perf/core: only check cpuctx with cgroup events during cgroup switch
Date: Sat, 31 Dec 2016 11:59:12 +0800 [thread overview]
Message-ID: <201612311119.FvItjpt4%fengguang.wu@intel.com> (raw)
In-Reply-To: <1483151475-6342-1-git-send-email-davidcc@google.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
Hi David,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.10-rc1 next-20161224]
[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/David-Carrillo-Cisneros/perf-core-only-check-cpuctx-with-cgroup-events-during-cgroup-switch/20161231-103433
config: x86_64-randconfig-s1-12311108 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
kernel/events/core.c: In function 'perf_event_init_all_cpus':
kernel/events/core.c:10587: error: 'cgrp_cpuctx_list' undeclared (first use in this function)
kernel/events/core.c:10587: error: (Each undeclared identifier is reported only once
kernel/events/core.c:10587: error: for each function it appears in.)
>> kernel/events/core.c:10587: error: type defaults to 'int' in declaration of 'type name'
>> kernel/events/core.c:10587: warning: cast from pointer to integer of different size
>> kernel/events/core.c:10587: error: type defaults to 'int' in declaration of 'type name'
vim +10587 kernel/events/core.c
10581 mutex_init(&swhash->hlist_mutex);
10582 INIT_LIST_HEAD(&per_cpu(active_ctx_list, cpu));
10583
10584 INIT_LIST_HEAD(&per_cpu(pmu_sb_events.list, cpu));
10585 raw_spin_lock_init(&per_cpu(pmu_sb_events.lock, cpu));
10586
10587 INIT_LIST_HEAD(&per_cpu(cgrp_cpuctx_list, cpu));
10588 INIT_LIST_HEAD(&per_cpu(sched_cb_list, cpu));
10589 }
10590 }
---
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: 23819 bytes --]
prev parent reply other threads:[~2016-12-31 3:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 2:31 David Carrillo-Cisneros
2016-12-31 3:03 ` kbuild test robot
2016-12-31 3:59 ` 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=201612311119.FvItjpt4%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=vikas.shivappa@linux.intel.com \
--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
all inboxes | Powered by JetHome®