All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Jeons <simon.jeons@gmail.com>
To: Mitsuhiro Tanino <mitsuhiro.tanino.gm@hitachi.com>
Cc: Ric Mason <ric.masonn@gmail.com>,
	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: Wed, 17 Apr 2013 13:49:46 +0800	[thread overview]
Message-ID: <516E37FA.4020000@gmail.com> (raw)
In-Reply-To: <51680F97.3020407@hitachi.com>

Hi Mitsuhiro,
On 04/12/2013 09:43 PM, Mitsuhiro Tanino wrote:
> (2013/04/11 22:00), Ric Mason wrote:
>> Hi Mitsuhiro,
>> On 04/11/2013 08:51 PM, Mitsuhiro Tanino wrote:
>>> (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.
>> Memory Scrubbing is a kernel thread? Where is the codes of memory scrubbing?
> Hi Ric,
>
> No. One of the MCA Recovery features is Memory Scrubbing.

Memory Scrubbing is a process in CPU?

> And Memory Scrubbing is a hardware feature of Intel CPU.
>
> OS has a hwpoison feature which is included at mm/memory-failure.c.
> A main function is memory_failure().
>
> If Memory Scrubbing finds a memory error, MCA recovery notifies SRAO error
> into OS and OS handles the SRAO error using hwpoison function.
>
>
>>> If Memory Scrubbing find an uncorrectable error on a memory before
>>> OS accesses the memory bit, MCA recovery notifies SRAO error into OS
>> It maybe can't find memory error timely since it is sleeping when memory error occur, can this case happened?
> Memory Scrubbing seems to be operated periodically but I don't have
> information about how oftern it is executed.

If Memory Scurbbing doesn't catch memory error timely, who will send 
SRAR into OS?

>
> 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>

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Simon Jeons <simon.jeons@gmail.com>
To: Mitsuhiro Tanino <mitsuhiro.tanino.gm@hitachi.com>
Cc: Ric Mason <ric.masonn@gmail.com>,
	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: Wed, 17 Apr 2013 13:49:46 +0800	[thread overview]
Message-ID: <516E37FA.4020000@gmail.com> (raw)
In-Reply-To: <51680F97.3020407@hitachi.com>

Hi Mitsuhiro,
On 04/12/2013 09:43 PM, Mitsuhiro Tanino wrote:
> (2013/04/11 22:00), Ric Mason wrote:
>> Hi Mitsuhiro,
>> On 04/11/2013 08:51 PM, Mitsuhiro Tanino wrote:
>>> (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.
>> Memory Scrubbing is a kernel thread? Where is the codes of memory scrubbing?
> Hi Ric,
>
> No. One of the MCA Recovery features is Memory Scrubbing.

Memory Scrubbing is a process in CPU?

> And Memory Scrubbing is a hardware feature of Intel CPU.
>
> OS has a hwpoison feature which is included at mm/memory-failure.c.
> A main function is memory_failure().
>
> If Memory Scrubbing finds a memory error, MCA recovery notifies SRAO error
> into OS and OS handles the SRAO error using hwpoison function.
>
>
>>> If Memory Scrubbing find an uncorrectable error on a memory before
>>> OS accesses the memory bit, MCA recovery notifies SRAO error into OS
>> It maybe can't find memory error timely since it is sleeping when memory error occur, can this case happened?
> Memory Scrubbing seems to be operated periodically but I don't have
> information about how oftern it is executed.

If Memory Scurbbing doesn't catch memory error timely, who will send 
SRAR into OS?

>
> 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-17  5:49 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11  3:26 [RFC Patch 0/2] mm: Add parameters to make kernel behavior at memory error on dirty cache selectable Mitsuhiro Tanino
2013-04-11  3:26 ` Mitsuhiro Tanino
2013-04-11  3:53 ` Simon Jeons
2013-04-11  3:53   ` Simon Jeons
2013-04-11 12:51   ` Mitsuhiro Tanino
2013-04-11 12:51     ` Mitsuhiro Tanino
2013-04-11 13:00     ` Ric Mason
2013-04-11 13:00       ` Ric Mason
2013-04-12 13:43       ` Mitsuhiro Tanino
2013-04-12 13:43         ` Mitsuhiro Tanino
2013-04-17  5:49         ` Simon Jeons [this message]
2013-04-17  5:49           ` Simon Jeons
2013-04-11  7:11 ` Naoya Horiguchi
2013-04-11  7:11   ` Naoya Horiguchi
2013-04-12 13:24   ` Mitsuhiro Tanino
2013-04-12 13:24     ` Mitsuhiro Tanino
2013-04-12 14:45     ` Naoya Horiguchi
2013-04-12 14:45       ` Naoya Horiguchi
2013-04-17  7:14   ` Simon Jeons
2013-04-17  7:14     ` Simon Jeons
2013-04-17 14:55     ` Naoya Horiguchi
2013-04-17 14:55       ` Naoya Horiguchi
2013-04-18  0:27       ` Simon Jeons
2013-04-18  0:27         ` Simon Jeons
2013-04-11 13:49 ` Andi Kleen
2013-04-11 13:49   ` Andi Kleen
2013-04-11 15:23   ` Naoya Horiguchi
2013-04-11 15:23     ` Naoya Horiguchi
2013-04-11 18:10     ` Andi Kleen
2013-04-11 18:10       ` Andi Kleen
2013-04-12 13:38       ` Mitsuhiro Tanino
2013-04-12 13:38         ` Mitsuhiro Tanino
2013-04-12 15:13         ` Naoya Horiguchi
2013-04-12 15:13           ` Naoya Horiguchi
2013-04-17 13:58           ` Naoya Horiguchi
2013-04-17 13:58             ` Naoya Horiguchi
2013-04-17  6:42     ` Simon Jeons
2013-04-17  6:42       ` Simon Jeons
2013-04-17 14:16       ` Naoya Horiguchi
2013-04-17 14:16         ` Naoya Horiguchi
2013-04-17  5:30   ` Simon Jeons
2013-04-17  5:30     ` Simon Jeons
2013-04-11 15:15 ` KOSAKI Motohiro
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=516E37FA.4020000@gmail.com \
    --to=simon.jeons@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mitsuhiro.tanino.gm@hitachi.com \
    --cc=ric.masonn@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 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.