From: Keir Fraser <keir@xensource.com>
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
Cc: Gavin.Maltby@sun.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] 3/3: MCA/MCE correctable error handling
Date: Wed, 22 Aug 2007 17:10:24 +0100 [thread overview]
Message-ID: <C2F21E80.1476F%keir@xensource.com> (raw)
In-Reply-To: <C2F21D68.1476D%keir@xensource.com>
On 22/8/07 17:05, "Keir Fraser" <keir@xensource.com> wrote:
>> The polling routine that is in the -unstable tree (the version taken from
>> Linux) runs every 15 seconds without adjustments.
>> 1Hz causes too much system load for a healthy system IMO.
>> That's why I introduced the adjustments with use of hw threshold registers
>> to come to a compromise solution.
>
> What's the deal here? Do correctable errors not cause an MCE, yet are still
> detected via the machine-check architecture (albeit by a polling method)?
>
> Are there going to be patches on the Linux side to pick up this MCA info?
> What is Linux going to do with it, apart from log it (which Xen can already
> do itself)? Or is this all Solaris-specific?
Oh, and is AMD-specific code really needed in non-fatal.c? I though the MCA
stuff was architectural now rather than vendor specific? If there are
vendor-specific extensions then they belong in the vendor's .c file.
-- Keir
next prev parent reply other threads:[~2007-08-22 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 13:31 [PATCH] 3/3: MCA/MCE correctable error handling Christoph Egger
2007-08-21 16:02 ` Jan Beulich
2007-08-22 9:00 ` Christoph Egger
2007-08-22 10:09 ` Jan Beulich
2007-08-22 15:56 ` Christoph Egger
2007-08-22 16:05 ` Keir Fraser
2007-08-22 16:10 ` Keir Fraser [this message]
2007-08-23 6:57 ` Christoph Egger
2007-08-23 9:27 ` [PATCH] resend " Christoph Egger
2007-08-23 14:07 ` [PATCH] " 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=C2F21E80.1476F%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.