From: Andi Kleen <ak@linux.intel.com>
To: Chen Yucong <slaoub@gmail.com>
Cc: fengguang.wu@intel.com, n-horiguchi@ah.jp.nec.com, linux-mm@kvack.org
Subject: Re: [PATCH] HWPOISON: avoid repeatedly raising some MCEs for a shared page
Date: Thu, 15 May 2014 07:38:05 -0700 [thread overview]
Message-ID: <20140515143805.GB19657@tassilo.jf.intel.com> (raw)
In-Reply-To: <1400152576-32004-1-git-send-email-slaoub@gmail.com>
On Thu, May 15, 2014 at 07:16:16PM +0800, Chen Yucong wrote:
> We assume that there have three processes P1, P2, and P3 which share a
> page frame PF0. PF0 have a multi-bit error that has not yet been detected.
How likely is that? Did you see it in some real case?
> As
> a result, P1/P2 may raise the same MCE again.
And how is that a problem?
The memory error handling is always somewhat probabilistic. There are a
lot of corner cases that could be be handled, but it would
be even more complex than it already is, and most of them are unlikely
to happen. The more complexity the more risk of unintended bugs.
So the question is always how likely that case is, and is it worth
handling. It's far better to focus on the common case.
Another concern is always how to test this. Usually all explicit paths
should have test cases in mce-test.
But it's not clear to me the additional complexity here is justified.
-andi
--
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>
next prev parent reply other threads:[~2014-05-15 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 11:16 [PATCH] HWPOISON: avoid repeatedly raising some MCEs for a shared page Chen Yucong
2014-05-15 14:38 ` Andi Kleen [this message]
2014-05-15 14:52 ` Naoya Horiguchi
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=20140515143805.GB19657@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=slaoub@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