public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Don Zickus <dzickus@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	"ying.huang@intel.com" <ying.huang@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
	"avi@redhat.com" <avi@redhat.com>,
	"jeremy@goop.org" <jeremy@goop.org>
Subject: Re: [V7][PATCH 0/6] x86, nmi: new NMI handling routines
Date: Tue, 4 Oct 2011 17:05:31 +0200	[thread overview]
Message-ID: <20111004150531.GH21506@erda.amd.com> (raw)
In-Reply-To: <1317657548.20367.33.camel@twins>

On 03.10.11 11:59:08, Peter Zijlstra wrote:
> I didn't need that, I build an allnoconfig (which got me a fail with the
> IBS patches), then an allyesconfig (which got me the earlier fail) and
> this came from my regular config which included the ipmi crap because
> Ingo hit this same fail earlier (-v5 or so) and everybody forgot to tell
> you :/

A change like the one below should fix the IBS build breakage (for
perf, x86: Implement IBS initialization).

-Robert


commit b670049b76a233599ebf64aff16cb8735fe6dc70
Author: Robert Richter <robert.richter@amd.com>
Date:   Tue Oct 4 16:51:54 2011 +0200

    perf, x86: Fix allnoconfig build error for ibs
    
     arch/x86/kernel/cpu/perf_event_amd_ibs.c: In function ‘get_eilvt’:
     arch/x86/kernel/cpu/perf_event_amd_ibs.c:90: error: implicit declaration of function ‘setup_APIC_eilvt’
    
    Signed-off-by: Robert Richter <robert.richter@amd.com>

diff --git a/arch/x86/kernel/cpu/perf_event_amd_ibs.c b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
index 1ae5154..cca9e0c 100644
--- a/arch/x86/kernel/cpu/perf_event_amd_ibs.c
+++ b/arch/x86/kernel/cpu/perf_event_amd_ibs.c
@@ -9,6 +9,7 @@
 #include <linux/perf_event.h>
 #include <linux/module.h>
 #include <linux/pci.h>
+#include <asm/apic.h>
 
 static u32 ibs_caps;
 


-- 
Advanced Micro Devices, Inc.
Operating System Research Center


  reply	other threads:[~2011-10-04 15:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 19:06 [V7][PATCH 0/6] x86, nmi: new NMI handling routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 1/6] x86, nmi: split out nmi from traps.c Don Zickus
2011-09-30 19:06 ` [V7][PATCH 2/6] x86, nmi: create new NMI handler routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 3/6] x86, nmi: wire up NMI handlers to new routines Don Zickus
2011-09-30 19:06 ` [V7][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Don Zickus
2011-09-30 19:06 ` [V7][PATCH 5/6] x86, nmi: track NMI usage stats Don Zickus
2011-09-30 19:06 ` [V7][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts Don Zickus
2011-10-03 15:47 ` [V7][PATCH 0/6] x86, nmi: new NMI handling routines Peter Zijlstra
2011-10-03 15:52 ` Peter Zijlstra
2011-10-03 15:56   ` Don Zickus
2011-10-03 15:59     ` Peter Zijlstra
2011-10-04 15:05       ` Robert Richter [this message]
2011-10-04 16:43         ` 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=20111004150531.GH21506@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    /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