From: Oscar Salvador <osalvador@suse.de>
To: Aili Yao <yaoaili@kingsoft.com>
Cc: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"yangfeng1@kingsoft.com" <yangfeng1@kingsoft.com>
Subject: Re: [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early
Date: Mon, 18 Jan 2021 11:09:32 +0100 [thread overview]
Message-ID: <20210118100928.GA4988@linux> (raw)
In-Reply-To: <20210118173852.0c784aa9.yaoaili@kingsoft.com>
On Mon, Jan 18, 2021 at 05:38:52PM +0800, Aili Yao wrote:
> On Mon, 18 Jan 2021 10:24:23 +0100
> Oscar Salvador <osalvador@suse.de> wrote:
>
> >
> > So, the scenario case is a multithread application with the same page mapped.
> > And PF_MCE_KILL_EARLY flag was set.
> >
> The scenario is not related multithread application;
> it's about multiprocess application which share the same page
Ok, I misunderstood that part.
Then, I do not fully understand the concern.
I guess you are kind of memory scrubbing with mcelog defaulting to
memory_failure instead of soft_offline.
E.g: collect_procs_anon will pick the processes which have the MCE policy
set and have the page mapped. That is all we should need.
So, if you have processes A, B, C and D with X page mapped, and you set
the MCE policy on those four, they should get picked up by your scrubbing
when handling X page by memory_failure.
Is not that right?
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-01-18 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:55 [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early Aili Yao
2021-01-15 8:49 ` Oscar Salvador
2021-01-15 9:26 ` Aili Yao
2021-01-15 9:31 ` Aili Yao
2021-01-15 9:40 ` Oscar Salvador
2021-01-15 9:53 ` Aili Yao
2021-01-15 10:31 ` Oscar Salvador
2021-01-18 5:15 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 5:57 ` Aili Yao
2021-01-18 6:50 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 7:16 ` Aili Yao
2021-01-18 8:15 ` Aili Yao
2021-01-18 8:57 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:09 ` Aili Yao
2021-01-19 5:25 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-19 6:04 ` Aili Yao
2021-01-19 7:33 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:24 ` Oscar Salvador
2021-01-18 9:38 ` Aili Yao
2021-01-18 10:09 ` Oscar Salvador [this message]
2021-01-19 4:21 ` Aili Yao
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=20210118100928.GA4988@linux \
--to=osalvador@suse.de \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=yangfeng1@kingsoft.com \
--cc=yaoaili@kingsoft.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.