From: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"Luck, Tony" <tony.luck@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Lutomirski, Andy" <luto@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <naoya.horiguchi@nec.com>
Cc: "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
"open list:HWPOISON MEMORY FAILURE HANDLING" <linux-mm@kvack.org>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/1] x86/mm: Forbid the zero page once it has uncorrectable errors
Date: Thu, 21 Apr 2022 07:53:58 +0000 [thread overview]
Message-ID: <DM8PR11MB566941C063EA44929147035E89F49@DM8PR11MB5669.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3720f7d9-a4f3-214c-1dea-f8ffc837c1da@intel.com>
> From: Hansen, Dave <dave.hansen@intel.com>
> ...
> Subject: Re: [PATCH 1/1] x86/mm: Forbid the zero page once it has
> uncorrectable errors
> ...
> There are lots of pages which are entirely fatal if they have uncorrectable errors.
> On my laptop, if there were an error, there is a 0.00000596% chance it will be in
> the zero page.
>
> Why is this worth special casing this one page?
Hi Dave,
Yes, this is a rare problem. Just feel that the fix is simple, so post it here to see whether you'll consider it 😊.
Thanks!
-Qiuxu
next prev parent reply other threads:[~2022-04-21 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 21:00 Qiuxu Zhuo
2022-04-20 13:39 ` Dave Hansen
2022-04-21 7:53 ` Zhuo, Qiuxu [this message]
2022-04-21 8:50 ` David Hildenbrand
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=DM8PR11MB566941C063EA44929147035E89F49@DM8PR11MB5669.namprd11.prod.outlook.com \
--to=qiuxu.zhuo@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=naoya.horiguchi@nec.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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