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>,
Vegard Nossum <vegard.nossum@gmail.com>,
Paul Turner <pjt@google.com>,
Stephane Eranian <eranian@google.com>,
David Carrillo-Cisneros <davidcc@google.com>
Subject: Re: [PATCH] perf/core: set cgroup for cpu contexts for new cgroup events
Date: Tue, 2 Aug 2016 11:30:26 +0800 [thread overview]
Message-ID: <201608021123.uwWCr1Ud%fengguang.wu@intel.com> (raw)
In-Reply-To: <1470107099-132631-1-git-send-email-davidcc@google.com>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
Hi David,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7 next-20160801]
[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-set-cgroup-for-cpu-contexts-for-new-cgroup-events/20160802-110924
config: x86_64-randconfig-x012-201631 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
kernel/events/core.c: In function 'list_add_event':
>> kernel/events/core.c:1428:24: error: 'struct perf_event' has no member named 'cgrp'
cpuctx->cgrp = event->cgrp;
^~
vim +1428 kernel/events/core.c
1422 if (!ctx->nr_cgroups++) {
1423 /*
1424 * Because cgroup events are always per-cpu events,
1425 * this will always be called from the right CPU.
1426 */
1427 cpuctx = __get_cpu_context(ctx);
> 1428 cpuctx->cgrp = event->cgrp;
1429 }
1430 }
1431
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23892 bytes --]
next prev parent reply other threads:[~2016-08-02 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 3:04 [PATCH] perf/core: set cgroup for cpu contexts for new cgroup events David Carrillo-Cisneros
2016-08-02 3:30 ` kbuild test robot [this message]
2016-08-02 7:21 ` David Carrillo-Cisneros
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=201608021123.uwWCr1Ud%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ak@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=tglx@linutronix.de \
--cc=vegard.nossum@gmail.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 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.