From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] x86: machine check exception handling Date: Thu, 21 Jun 2007 15:59:47 +0100 Message-ID: References: <200706211638.47367.Christoph.Egger@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200706211638.47367.Christoph.Egger@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Egger , xen-devel@lists.xensource.com Cc: Gavin Maltby , Keir Fraser , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 21/6/07 15:38, "Christoph Egger" wrote: > That's not possible. The #MC handler and the polling handler (in non-fatal.c) > (are going to) do something completely different than any OS will ever do. > See the discussion with the subject "MCA/MCE concept" for more information. Well, then I guess these files will change wholesale when this new MCE architecture is ready. That's fine. > In opposition to the polling handler, #MC interruption is *very* bad. > A #MC always means, that an uncorrectable ECC error is detected > by the hw. First you have to figure out, who is impacted: Is it Xen, Dom0 or > DomU? > In case of Xen and Dom0 you can only do something using hw correction > features or crash. In case of DomU, you can kill DomU in the worst case > and keep the rest running. If the error is such that it will impact correct execution of a Xen interrupt handler (which generally do very little indeed) then you are boned. Your #MC handler is unlikely to work properly either. Game over. And you already know my opinion of the new "MCA/MCE concept". -- Keir