From: "H. Peter Anvin" <hpa@zytor.com>
To: Max Asbock <masbock@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, mingo@redhat.com
Subject: Re: x86 32-bit machine check handler
Date: Mon, 12 Nov 2007 13:20:46 -0800 [thread overview]
Message-ID: <4738C3AE.1070104@zytor.com> (raw)
In-Reply-To: <1194899975.9979.7.camel@w-amax.beaverton.ibm.com>
Max Asbock wrote:
> Now that the 32-bit and 64-bit x86 machine check handlers live next to
> each other a certain asymmetry in functionality is apparent. Notably,
> the 64-bit machine check handler implements a timer that periodically
> polls for silent machine check errors and makes them accessible to user
> space through /dev/mcelog. Are there reasons the x86 32-bit machine
> check handler couldn't do the same?
No, and in fact, it should.
-hpa
next prev parent reply other threads:[~2007-11-12 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 20:39 x86 32-bit machine check handler Max Asbock
2007-11-12 21:20 ` H. Peter Anvin [this message]
2007-11-13 14:15 ` Andi Kleen
2007-11-15 1:06 ` Max Asbock
2007-11-15 5:36 ` Andi Kleen
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=4738C3AE.1070104@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masbock@us.ibm.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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