public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Don Zickus <dzickus@redhat.com>
Cc: x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
	Robert Richter <robert.richter@amd.com>,
	ying.huang@intel.com, LKML <linux-kernel@vger.kernel.org>,
	jason.wessel@windriver.com
Subject: Re: [RFC][PATCH 2/6] x86, nmi: create new NMI handler routines
Date: Mon, 22 Aug 2011 17:26:52 +0200	[thread overview]
Message-ID: <1314026812.24275.67.camel@twins> (raw)
In-Reply-To: <20110822152154.GB2067@redhat.com>

On Mon, 2011-08-22 at 11:21 -0400, Don Zickus wrote:
> 
> Sure.  Well there are a few drivers that want to register.  Unless you
> want to make a rule that all nmi handlers have to be built-in? 

Well, I'm all for that, but I guess I'm going to loose that particular
fight ;-)

  reply	other threads:[~2011-08-22 15:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 20:37 [RFC][PATCH 0/6] x86, nmi: new NMI handling routines Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 1/6] x86, nmi: split out nmi from traps.c Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 2/6] x86, nmi: create new NMI handler routines Don Zickus
2011-08-22 14:13   ` Peter Zijlstra
2011-08-22 15:21     ` Don Zickus
2011-08-22 15:26       ` Peter Zijlstra [this message]
2011-08-22 15:41         ` Don Zickus
2011-08-22 15:31       ` Peter Zijlstra
2011-08-22 14:16   ` Peter Zijlstra
2011-08-22 15:23     ` Don Zickus
2011-08-23 14:14     ` Don Zickus
2011-08-23 14:17       ` Peter Zijlstra
2011-08-24 17:04   ` Paul E. McKenney
2011-08-24 17:44     ` Don Zickus
2011-08-24 17:51       ` Peter Zijlstra
2011-08-24 18:16         ` Don Zickus
2011-08-24 18:19           ` Peter Zijlstra
2011-08-24 19:16             ` Paul E. McKenney
2011-08-19 20:37 ` [RFC][PATCH 3/6] x86, nmi: wire up NMI handlers to new routines Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Don Zickus
2011-08-22 14:22   ` Peter Zijlstra
2011-08-22 15:25     ` Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 5/6] x86, nmi: track NMI usage stats Don Zickus
2011-08-19 20:37 ` [RFC][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts Don Zickus
2011-08-22 14:27   ` Peter Zijlstra
2011-08-22 15:28     ` Don Zickus

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=1314026812.24275.67.camel@twins \
    --to=peterz@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=dzickus@redhat.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.richter@amd.com \
    --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