public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Olof Johansson <olof@lixom.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Corrupted low memory in v3.9+
Date: Mon, 11 Nov 2013 16:04:13 -0800	[thread overview]
Message-ID: <5281707D.1040604@linux.intel.com> (raw)
In-Reply-To: <528168CB.7070602@linux.intel.com>

On 11/11/2013 03:31 PM, H. Peter Anvin wrote:
> On 11/11/2013 03:35 AM, Ingo Molnar wrote:
> 
> Oops!  I had misunderstood how the checker worked -- I thought it
> checked the *reserved* memory, but it in fact reserves memory
> *independently* and then checks it.
> 

And now I understand why I had that misconception:

> 	  Periodically check for memory corruption in low memory, which
> 	  is suspected to be caused by BIOS.  Even when enabled in the
> 	  configuration, it is disabled at runtime.  Enable it by
> 	  setting "memory_corruption_check=1" on the kernel command
> 	  line.  By default it scans the low 64k of memory every 60
> 	  seconds; see the memory_corruption_check_size and
> 	  memory_corruption_check_period parameters in
> 	  Documentation/kernel-parameters.txt to adjust this.

This makes it sound like it scans the low 64K when it is turned on, i.e.
the bit that is reserved by default.

I think we should change that default too to 640K.  I will post a
patchset shortly.

	-hpa




      reply	other threads:[~2013-11-12  0:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 18:57 Corrupted low memory in v3.9+ Olof Johansson
2013-10-17 19:39 ` H. Peter Anvin
2013-10-17 20:39   ` Olof Johansson
2013-11-07 19:02     ` Olof Johansson
2013-11-07 19:31       ` H. Peter Anvin
2013-11-11 11:35         ` Ingo Molnar
2013-11-11 23:31           ` H. Peter Anvin
2013-11-12  0:04             ` H. Peter Anvin [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=5281707D.1040604@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=olof@lixom.net \
    /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