linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Oscar Salvador <osalvador@suse.de>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH 2/4] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range()
Date: Tue, 30 Jul 2024 12:26:24 +0200	[thread overview]
Message-ID: <b8d46144-ccb3-4f90-96bc-8818c69df471@redhat.com> (raw)
In-Reply-To: <20240725011647.1306045-3-wangkefeng.wang@huawei.com>

On 25.07.24 03:16, Kefeng Wang wrote:
> The commit b15c87263a69 ("hwpoison, memory_hotplug: allow hwpoisoned
> pages to be offlined") don't handle the hugetlb pages, the dead loop
> still occur if offline a hwpoison hugetlb, luckly, after the commit
> e591ef7d96d6 ("mm,hwpoison,hugetlb,memory_hotplug: hotremove memory
> section with hwpoisoned hugepage"), the HPageMigratable of hugetlb
> page will be clear, and the hwpoison hugetlb page will be skipped in
> scan_movable_pages(), so the deed loop issue is fixed.

did you mean "endless loop" ?

> 
> However if the HPageMigratable() check passed(without reference and
> lock), the hugetlb page may be hwpoisoned, it won't cause issue since
> the hwpoisoned page will be handled correctly in the next movable
> pages scan loop, and it will be isolated in do_migrate_range() and
> but fails to migrated. In order to avoid the unnecessary isolation and
> unify all hwpoisoned page handling, let's unconditionally check hwpoison
> firstly, and if it is a hwpoisoned hugetlb page, try to unmap it as
> the catch all safety net like normal page does.

But what's the benefit here besides slightly faster handling in an 
absolute corner case (I strongly suspect that we don't care)?

> 
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
>   mm/memory_hotplug.c | 27 ++++++++++++++++-----------
>   1 file changed, 16 insertions(+), 11 deletions(-)
> 
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 66267c26ca1b..ccaf4c480aed 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -1788,28 +1788,33 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
>   		folio = page_folio(page);
>   		head = &folio->page;
>   
> -		if (PageHuge(page)) {
> -			pfn = page_to_pfn(head) + compound_nr(head) - 1;
> -			isolate_hugetlb(folio, &source);
> -			continue;
> -		} else if (PageTransHuge(page))
> -			pfn = page_to_pfn(head) + thp_nr_pages(page) - 1;
> -
>   		/*
>   		 * HWPoison pages have elevated reference counts so the migration would
>   		 * fail on them. It also doesn't make any sense to migrate them in the
>   		 * first place. Still try to unmap such a page in case it is still mapped
> -		 * (e.g. current hwpoison implementation doesn't unmap KSM pages but keep
> -		 * the unmap as the catch all safety net).
> +		 * (keep the unmap as the catch all safety net).
>   		 */
> -		if (PageHWPoison(page)) {
> +		if (unlikely(PageHWPoison(page))) {

We're not checking the head page here, will this work reliably for 
hugetlb? (I recall some difference in per-page hwpoison handling between 
hugetlb and THP due to the vmemmap optimization)


-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-07-30 10:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  1:16 [PATCH 0/4] mm: memory_hotplug: improve do_migrate_range() Kefeng Wang
2024-07-25  1:16 ` [PATCH 1/4] mm: memory-failure: add unmap_posioned_folio() Kefeng Wang
2024-07-30 10:20   ` David Hildenbrand
2024-07-31  4:46     ` Kefeng Wang
2024-07-25  1:16 ` [PATCH 2/4] mm: memory_hotplug: check hwpoisoned page firstly in do_migrate_range() Kefeng Wang
2024-07-30 10:26   ` David Hildenbrand [this message]
2024-07-31  5:09     ` Kefeng Wang
2024-08-01 20:10       ` David Hildenbrand
2024-08-02  7:50         ` Kefeng Wang
2024-08-06  9:29           ` David Hildenbrand
     [not found]             ` <1e6cccc5-fedc-8df6-1deb-16ceb52a4094@huawei.com>
     [not found]               ` <1e14d86d-0d17-41da-9400-16c9c6f93f8f@redhat.com>
2024-08-09  2:02                 ` Miaohe Lin
2024-08-01 20:14   ` David Hildenbrand
2024-08-02  8:02     ` Kefeng Wang
2024-08-06  3:44       ` Kefeng Wang
2024-08-06  9:24         ` David Hildenbrand
2024-08-06  9:15       ` David Hildenbrand
2024-07-25  1:16 ` [PATCH 3/4] mm: migrate: add isolate_folio_to_list() Kefeng Wang
2024-07-26 14:21   ` kernel test robot
2024-07-27  7:56     ` Kefeng Wang
2024-07-30 10:30   ` David Hildenbrand
2024-07-25  1:16 ` [PATCH 4/4] mm: memory_hotplug: unify Huge/LRU/non-LRU movable folio isolation Kefeng Wang
2024-07-30 10:31   ` David Hildenbrand
2024-07-31  5:13     ` Kefeng Wang
2024-08-01 20:16       ` David Hildenbrand
2024-08-01 20:23   ` David Hildenbrand
2024-08-02  8:39     ` Kefeng Wang

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=b8d46144-ccb3-4f90-96bc-8818c69df471@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=wangkefeng.wang@huawei.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