Date: Fri, 13 May 2011 17:20:33 +0200
From: Ingo Molnar <mingo@elte.hu>
To: huang ying <huang.ying.caritas@gmail.com>
Cc: Don Zickus <dzickus@redhat.com>, Huang Ying <ying.huang@intel.com>,
        linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
        Robert Richter <robert.richter@amd.com>,
        Andi Kleen <ak@linux.intel.com>, Borislav Petkov <bp@alien8.de>
Subject: Re: [RFC] x86, NMI, Treat unknown NMI as hardware error
Message-ID: <20110513152033.GB3854@elte.hu>
References: <1305275018-20596-1-git-send-email-ying.huang@intel.com>
 <20110513124523.GM13984@redhat.com>
 <20110513130011.GA6474@elte.hu>
 <BANLkTi=Z_3MZVs2CQyk82NfvZj-KdSw5kw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BANLkTi=Z_3MZVs2CQyk82NfvZj-KdSw5kw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1028
Lines: 29


* huang ying <huang.ying.caritas@gmail.com> wrote:

> > What should be done instead is to add an event for unknown NMIs, which can 
> > then be processed by the RAS daemon to implement policy.
> >
> > By using 'active' event filters it could even be set on a system to panic 
> > the box by default.
> 
> If there is real fatal hardware error, maybe we have no luxury to go from NMI 
> handler to user space RAS daemon to determine what to do. System may explode, 
> bad data may go to disk before that.

That is why i suggested:

  > > By using 'active' event filters it could even be set on a system to panic 
  > > the box by default.

event filters are evaluated in the kernel, so the panic could be instantaneous, 
without the event having to reach user-space.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/