From: kbuild test robot <lkp@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, acme@redhat.com,
peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
kan.liang@intel.com, jolsa@redhat.com, namhyung@kernel.org,
adrian.hunter@intel.com
Subject: Re: [PATCH] perf/x86/pebs: catch all PEBS overflow conditions
Date: Fri, 11 Mar 2016 00:21:01 +0800 [thread overview]
Message-ID: <201603110046.qov3Lt9k%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457626092-29463-1-git-send-email-eranian@google.com>
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
Hi Stephane,
[auto build test ERROR on next-20160310]
[cannot apply to tip/x86/core v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Stephane-Eranian/perf-x86-pebs-catch-all-PEBS-overflow-conditions/20160311-001126
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/events//intel/core.c: In function 'intel_pmu_handle_irq':
>> arch/x86/events//intel/core.c:1910:3: error: 'orig_status' undeclared (first use in this function)
orig_status |= 1ULL << 62;
^
arch/x86/events//intel/core.c:1910:3: note: each undeclared identifier is reported only once for each function it appears in
vim +/orig_status +1910 arch/x86/events//intel/core.c
1904 * in the for_each_bit_set() loop for regular samples below.
1905 */
1906 status &= ~cpuc->pebs_enabled;
1907 status &= x86_pmu.intel_ctrl | GLOBAL_STATUS_TRACE_TOPAPMI;
1908
1909 /* make sure bit 62 is acked in any case */
> 1910 orig_status |= 1ULL << 62;
1911 }
1912
1913 /*
---
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: 6269 bytes --]
prev parent reply other threads:[~2016-03-10 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 16:08 [PATCH] perf/x86/pebs: catch all PEBS overflow conditions Stephane Eranian
2016-03-10 16:21 ` 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=201603110046.qov3Lt9k%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).