From: Miaohe Lin <linmiaohe@huawei.com>
To: Naoya Horiguchi <naoya.horiguchi@linux.dev>, <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Liu Shixin <liushixin2@huawei.com>,
Yang Shi <shy828301@gmail.com>,
Oscar Salvador <osalvador@suse.de>,
Muchun Song <songmuchun@bytedance.com>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [mm-unstable PATCH v6 4/8] mm, hwpoison: make unpoison aware of raw error info in hwpoisoned hugepage
Date: Wed, 13 Jul 2022 12:24:46 +0800 [thread overview]
Message-ID: <1ebd5240-7298-5d1d-cc1d-d289d843472d@huawei.com> (raw)
In-Reply-To: <20220712032858.170414-5-naoya.horiguchi@linux.dev>
On 2022/7/12 11:28, Naoya Horiguchi wrote:
> From: Naoya Horiguchi <naoya.horiguchi@nec.com>
>
> Raw error info list needs to be removed when hwpoisoned hugetlb is
> unpoisoned. And unpoison handler needs to know how many errors there
> are in the target hugepage. So add them.
>
> HPageVmemmapOptimized(hpage) and HPageRawHwpUnreliable(hpage)) can't be
> unpoisoned, so let's skip them.
>
> Signed-off-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
> Reported-by: kernel test robot <lkp@intel.com>
This patch looks good to me with some nits below.
> ---
...
>
> -void hugetlb_clear_page_hwpoison(struct page *hpage)
> +static unsigned long free_raw_hwp_pages(struct page *hpage, bool move_flag)
> {
> struct llist_head *head;
> struct llist_node *t, *tnode;
> + unsigned long count = 0;
>
> - if (!HPageRawHwpUnreliable(hpage))
> - ClearPageHWPoison(hpage);
> + /*
> + * HPageVmemmapOptimized hugepages can't be unpoisoned because
> + * struct pages for tail pages are required to free hwpoisoned
> + * hugepages. HPageRawHwpUnreliable hugepages shouldn't be
> + * unpoisoned by definition.
> + */
> + if (HPageVmemmapOptimized(hpage) || HPageRawHwpUnreliable(hpage))
If move_flag == false, i.e. in unpoison case, tail pages are not touched. So HPageVmemmapOptimized
can be ignored in this case? Or leave it as above to keep the code simple?
> + return 0;
> head = raw_hwp_list_head(hpage);
> llist_for_each_safe(tnode, t, head->first) {
> struct raw_hwp_page *p = container_of(tnode, struct raw_hwp_page, node);
>
> - SetPageHWPoison(p->page);
> + if (move_flag)
> + SetPageHWPoison(p->page);
> kfree(p);
> + count++;
> }
> llist_del_all(head);
> + return count;
> +}
> +
> +void hugetlb_clear_page_hwpoison(struct page *hpage)
> +{
> + if (!HPageRawHwpUnreliable(hpage))
It seems we can return here if HPageRawHwpUnreliable as there's nothing to do?
Anyway, for what it worth,
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks.
> + ClearPageHWPoison(hpage);
> + free_raw_hwp_pages(hpage, true);
> }
>
> /*
next prev parent reply other threads:[~2022-07-13 4:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 3:28 [mm-unstable PATCH v6 0/8] mm, hwpoison: enable 1GB hugepage support (v6) Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 1/8] mm/hugetlb: check gigantic_page_runtime_supported() in return_unused_surplus_pages() Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 2/8] mm/hugetlb: make pud_huge() and follow_huge_pud() aware of non-present pud entry Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 3/8] mm, hwpoison, hugetlb: support saving mechanism of raw error pages Naoya Horiguchi
2022-07-13 4:51 ` Miaohe Lin
2022-07-13 11:54 ` HORIGUCHI NAOYA(堀口 直也)
2022-07-12 3:28 ` [mm-unstable PATCH v6 4/8] mm, hwpoison: make unpoison aware of raw error info in hwpoisoned hugepage Naoya Horiguchi
2022-07-13 4:24 ` Miaohe Lin [this message]
2022-07-13 11:54 ` HORIGUCHI NAOYA(堀口 直也)
2022-07-12 3:28 ` [mm-unstable PATCH v6 5/8] mm, hwpoison: set PG_hwpoison for busy hugetlb pages Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 6/8] mm, hwpoison: make __page_handle_poison returns int Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 7/8] mm, hwpoison: skip raw hwpoison page in freeing 1GB hugepage Naoya Horiguchi
2022-07-12 3:28 ` [mm-unstable PATCH v6 8/8] mm, hwpoison: enable memory error handling on " 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=1ebd5240-7298-5d1d-cc1d-d289d843472d@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@linux.dev \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.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