All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Xishi Qiu <qiuxishi@huawei.com>
Subject: mce: a question about memory_failure_early_kill in memory_failure()
Date: Tue, 19 Apr 2016 19:13:34 +0800	[thread overview]
Message-ID: <571612DE.8020908@huawei.com> (raw)

/proc/sys/vm/memory_failure_early_kill

1: means kill all processes that have the corrupted and not reloadable page mapped.
0: means only unmap the corrupted page from all processes and only kill a process
who tries to access it.

If set memory_failure_early_kill to 0, and memory_failure() has been called.
memory_failure()
	hwpoison_user_mappings()
		collect_procs()  // the task(with no PF_MCE_PROCESS flag) is not in the tokill list
			try_to_unmap()

If the task access the memory, there will be a page fault,
so the task can not access the original page again, right?

Thanks,
Xishi Qiu

--
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: Xishi Qiu <qiuxishi@huawei.com>
To: Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Xishi Qiu <qiuxishi@huawei.com>
Subject: mce: a question about memory_failure_early_kill in memory_failure()
Date: Tue, 19 Apr 2016 19:13:34 +0800	[thread overview]
Message-ID: <571612DE.8020908@huawei.com> (raw)

/proc/sys/vm/memory_failure_early_kill

1: means kill all processes that have the corrupted and not reloadable page mapped.
0: means only unmap the corrupted page from all processes and only kill a process
who tries to access it.

If set memory_failure_early_kill to 0, and memory_failure() has been called.
memory_failure()
	hwpoison_user_mappings()
		collect_procs()  // the task(with no PF_MCE_PROCESS flag) is not in the tokill list
			try_to_unmap()

If the task access the memory, there will be a page fault,
so the task can not access the original page again, right?

Thanks,
Xishi Qiu

             reply	other threads:[~2016-04-19 11:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 11:13 Xishi Qiu [this message]
2016-04-19 11:13 ` mce: a question about memory_failure_early_kill in memory_failure() Xishi Qiu
2016-04-20  7:07 ` Naoya Horiguchi
2016-04-20  7:07   ` Naoya Horiguchi
2016-04-20 10:51   ` Xishi Qiu
2016-04-20 10:51     ` Xishi Qiu
2016-04-20 10:58     ` Xishi Qiu
2016-04-20 10:58       ` Xishi Qiu
2016-04-20 23:15       ` Naoya Horiguchi
2016-04-20 23:15         ` Naoya Horiguchi
2016-04-21  3:17         ` Xishi Qiu
2016-04-21  3:17           ` Xishi Qiu
2016-04-21  8:20         ` Xishi Qiu
2016-04-21  8:20           ` Xishi Qiu

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=571612DE.8020908@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.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.