From: Oscar Salvador <osalvador@suse.de>
To: Aili Yao <yaoaili@kingsoft.com>
Cc: naoya.horiguchi@nec.com, linux-mm@kvack.org, yangfeng1@kingsoft.com
Subject: Re: [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early
Date: Fri, 15 Jan 2021 10:40:37 +0100 [thread overview]
Message-ID: <20210115094037.GD4092@linux> (raw)
In-Reply-To: <20210115173125.078d8c13.yaoaili@kingsoft.com>
On Fri, Jan 15, 2021 at 05:31:25PM +0800, Aili Yao wrote:
> On Fri, 15 Jan 2021 17:26:22 +0800
> Aili Yao <yaoaili@kingsoft.com> wrote:
>
> > > So, back to your change, if force_early was set, but the main task does not
> > > match, you still want to check whether any thread belonging to the main task
> > > has the policy set?
> > >
> > Yes.
> >
> Sorry, the code only loop processes, not thread.
The loop in task_early_kill goes through processes, while the one in
find_early_kill_thread goes through threads, right?
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2021-01-15 9:40 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 [this message]
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
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=20210115094037.GD4092@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.