From: Randy Dunlap <rdunlap@infradead.org>
To: Paul Bolle <pebolle@tiscali.nl>, Andi Kleen <ak@linux.intel.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/Changes: cleanup mcelog paragraph
Date: Sat, 28 Jun 2014 18:35:37 -0700 [thread overview]
Message-ID: <53AF6D69.5060601@infradead.org> (raw)
In-Reply-To: <1403611956.1960.17.camel@x220>
On 06/24/14 05:12, Paul Bolle wrote:
> The paragraph on mcelog currently describes kernel v2.6.31. In that
> kernel the mce code (for i386, that is) was in transition. Ever since
> v2.6.32 the situation is much simpler (eg, mcelog is now needed to
> process events on almost all x86 machines, i386 and x86-64). Since this
> "document is designed to provide a list of the minimum levels of
> software necessary to run the 3.0 kernels" let's just describe that
> situation.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Documentation/Changes | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/Changes b/Documentation/Changes
> index 2254db0f00a5..227bec88021e 100644
> --- a/Documentation/Changes
> +++ b/Documentation/Changes
> @@ -280,12 +280,9 @@ that is possible.
> mcelog
> ------
>
> -In Linux 2.6.31+ the i386 kernel needs to run the mcelog utility
> -as a regular cronjob similar to the x86-64 kernel to process and log
> -machine check events when CONFIG_X86_NEW_MCE is enabled. Machine check
> -events are errors reported by the CPU. Processing them is strongly encouraged.
> -All x86-64 kernels since 2.6.4 require the mcelog utility to
> -process machine checks.
> +On x86 kernels the mcelog utility is needed to process and log machine check
> +events when CONFIG_X86_MCE is enabled. Machine check events are errors reported
> +by the CPU. Processing them is strongly encouraged.
>
> Getting updated software
> ========================
>
Applied with Andi's ack. Thanks.
--
~Randy
prev parent reply other threads:[~2014-06-29 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 12:12 [PATCH] Documentation/Changes: cleanup mcelog paragraph Paul Bolle
2014-06-24 17:42 ` Andi Kleen
2014-06-29 1:35 ` Randy Dunlap [this message]
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=53AF6D69.5060601@infradead.org \
--to=rdunlap@infradead.org \
--cc=ak@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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