From: zhenwei pi <pizhenwei@bytedance.com>
To: akpm@linux-foundation.org, naoya.horiguchi@nec.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhenwei pi <pizhenwei@bytedance.com>
Subject: [PATCH 0/4] memory-failure: fix hwpoison_filter
Date: Fri, 29 Apr 2022 22:22:02 +0800 [thread overview]
Message-ID: <20220429142206.294714-1-pizhenwei@bytedance.com> (raw)
Hi,
There are two parts in this series:
"move clear_hwpoisoned_pages" and "simplify num_poisoned_pages_dec"
do not fix bugs, just make memory failure easy to maintain.
"optimize hwpoison_filter" and "add hwpoison_filter for soft offline"
try to fix hwpoison_filter.
zhenwei pi (4):
mm/memory-failure.c: move clear_hwpoisoned_pages
mm/memofy-failure.c:: simplify num_poisoned_pages_dec
mm/memofy-failure.c: optimize hwpoison_filter
mm/memofy-failure.c: add hwpoison_filter for soft offline
mm/internal.h | 11 ++++++
mm/memory-failure.c | 81 ++++++++++++++++++++++++---------------------
mm/page_alloc.c | 1 -
mm/sparse.c | 27 ---------------
4 files changed, 54 insertions(+), 66 deletions(-)
--
2.20.1
next reply other threads:[~2022-04-29 14:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:22 zhenwei pi [this message]
2022-04-29 14:22 ` [PATCH 1/4] mm/memory-failure.c: move clear_hwpoisoned_pages zhenwei pi
2022-05-06 8:55 ` Naoya Horiguchi
2022-04-29 14:22 ` [PATCH 2/4] mm/memofy-failure.c:: simplify num_poisoned_pages_dec zhenwei pi
2022-05-06 8:55 ` Naoya Horiguchi
2022-04-29 14:22 ` [PATCH 3/4] mm/memofy-failure.c: optimize hwpoison_filter zhenwei pi
2022-05-06 8:59 ` Naoya Horiguchi
2022-05-06 13:38 ` zhenwei pi
2022-05-06 16:28 ` David Hildenbrand
2022-05-07 0:28 ` zhenwei pi
2022-05-07 8:20 ` Naoya Horiguchi
2022-05-07 9:19 ` zhenwei pi
2022-04-29 14:22 ` [PATCH 4/4] mm/memofy-failure.c: add hwpoison_filter for soft offline zhenwei pi
2022-05-06 8:59 ` 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=20220429142206.294714-1-pizhenwei@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).