All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Cc: Gavin Maltby <Gavin.Maltby@sun.com>,
	Keir Fraser <keir@xensource.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] x86: machine check exception handling
Date: Thu, 21 Jun 2007 15:59:47 +0100	[thread overview]
Message-ID: <C2A050F3.110A0%keir@xensource.com> (raw)
In-Reply-To: <200706211638.47367.Christoph.Egger@amd.com>

On 21/6/07 15:38, "Christoph Egger" <Christoph.Egger@amd.com> 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

  reply	other threads:[~2007-06-21 14:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 10:06 [PATCH] x86: machine check exception handling Jan Beulich
2007-06-21 14:15 ` Keir Fraser
2007-06-21 14:38   ` Christoph Egger
2007-06-21 14:59     ` Keir Fraser [this message]
2007-06-25 11:07       ` Christoph Egger
2007-06-22  6:57   ` Jan Beulich
2007-06-22  7:15     ` Keir Fraser
2007-06-22  7:47       ` Jan Beulich
2007-06-22  7:52         ` Keir Fraser
2007-06-22  7:59           ` Keir Fraser
2007-06-22  7:01   ` Jan Beulich
2007-06-22  7:16     ` Keir Fraser

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=C2A050F3.110A0%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Gavin.Maltby@sun.com \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.