linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mitsuhiro Tanino <mitsuhiro.tanino.gm@hitachi.com>
To: Simon Jeons <simon.jeons@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC Patch 0/2] mm: Add parameters to make kernel behavior at memory error on dirty cache selectable
Date: Thu, 11 Apr 2013 21:51:43 +0900	[thread overview]
Message-ID: <5166B1DF.8070504@hitachi.com> (raw)
In-Reply-To: <516633BB.40307@gmail.com>

(2013/04/11 12:53), Simon Jeons wrote:
> One question against mce instead of the patchset. ;-)
> 
> When check memory is bad? Before memory access? Is there a process scan it period?

Hi Simon-san,

Yes, there is a process to scan memory periodically.

At Intel Nehalem-EX and CPUs after Nehalem-EX generation, MCA recovery
is supported. MCA recovery provides error detection and isolation
features to work together with OS.
One of the MCA Recovery features is Memory Scrubbing. It periodically
checks memory in the background of OS.

If Memory Scrubbing find an uncorrectable error on a memory before
OS accesses the memory bit, MCA recovery notifies SRAO error into OS 
and OS handles the SRAO error using hwpoison function.

Regards,
Mitsuhiro Tanino

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

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

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11  3:26 Mitsuhiro Tanino
2013-04-11  3:53 ` Simon Jeons
2013-04-11 12:51   ` Mitsuhiro Tanino [this message]
2013-04-11 13:00     ` Ric Mason
2013-04-12 13:43       ` Mitsuhiro Tanino
2013-04-17  5:49         ` Simon Jeons
2013-04-11  7:11 ` Naoya Horiguchi
2013-04-12 13:24   ` Mitsuhiro Tanino
2013-04-12 14:45     ` Naoya Horiguchi
2013-04-17  7:14   ` Simon Jeons
2013-04-17 14:55     ` Naoya Horiguchi
2013-04-18  0:27       ` Simon Jeons
2013-04-11 13:49 ` Andi Kleen
2013-04-11 15:23   ` Naoya Horiguchi
2013-04-11 18:10     ` Andi Kleen
2013-04-12 13:38       ` Mitsuhiro Tanino
2013-04-12 15:13         ` Naoya Horiguchi
2013-04-17 13:58           ` Naoya Horiguchi
2013-04-17  6:42     ` Simon Jeons
2013-04-17 14:16       ` Naoya Horiguchi
2013-04-17  5:30   ` Simon Jeons
2013-04-11 15:15 ` KOSAKI Motohiro

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=5166B1DF.8070504@hitachi.com \
    --to=mitsuhiro.tanino.gm@hitachi.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=simon.jeons@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox