From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH v1 1/6] mm/huge_memory: convert has_hwpoisoned into a pure folio flag
Date: Fri, 10 Jan 2025 19:21:44 +0100 [thread overview]
Message-ID: <20250110182149.746551-2-david@redhat.com> (raw)
In-Reply-To: <20250110182149.746551-1-david@redhat.com>
Let's stop setting it on pages, there is no need to anymore.
Signed-off-by: David Hildenbrand <david@redhat.com>
---
include/linux/page-flags.h | 6 ++----
mm/huge_memory.c | 2 +-
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
index 14226d6bd6f84..3f6a64ff968a7 100644
--- a/include/linux/page-flags.h
+++ b/include/linux/page-flags.h
@@ -948,11 +948,9 @@ TESTPAGEFLAG_FALSE(TransCompound, transcompound)
*
* This flag is set by hwpoison handler. Cleared by THP split or free page.
*/
-PAGEFLAG(HasHWPoisoned, has_hwpoisoned, PF_SECOND)
- TESTSCFLAG(HasHWPoisoned, has_hwpoisoned, PF_SECOND)
+FOLIO_FLAG(has_hwpoisoned, FOLIO_SECOND_PAGE)
#else
-PAGEFLAG_FALSE(HasHWPoisoned, has_hwpoisoned)
- TESTSCFLAG_FALSE(HasHWPoisoned, has_hwpoisoned)
+FOLIO_FLAG_FALSE(has_hwpoisoned)
#endif
/*
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 2654a95487499..3d3ebdc002d59 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -3290,7 +3290,7 @@ static void __split_huge_page(struct page *page, struct list_head *list,
/* lock lru list/PageCompound, ref frozen by page_ref_freeze */
lruvec = folio_lruvec_lock(folio);
- ClearPageHasHWPoisoned(head);
+ folio_clear_has_hwpoisoned(folio);
for (i = nr - new_nr; i >= new_nr; i -= new_nr) {
struct folio *tail;
--
2.47.1
next prev parent reply other threads:[~2025-01-10 18:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 18:21 [PATCH v1 0/6] mm/hugetlb: folio and migration cleanups David Hildenbrand
2025-01-10 18:21 ` David Hildenbrand [this message]
2025-01-10 18:39 ` [PATCH v1 1/6] mm/huge_memory: convert has_hwpoisoned into a pure folio flag Matthew Wilcox
2025-01-10 18:21 ` [PATCH v1 2/6] mm/hugetlb: rename isolate_hugetlb() to folio_isolate_hugetlb() David Hildenbrand
2025-01-10 18:41 ` Matthew Wilcox
2025-01-13 12:25 ` Baolin Wang
2025-01-10 18:21 ` [PATCH v1 3/6] mm/migrate: don't call folio_putback_active_hugetlb() on dst hugetlb folio David Hildenbrand
2025-01-13 7:00 ` Baolin Wang
2025-01-13 9:50 ` David Hildenbrand
2025-01-13 12:21 ` Baolin Wang
2025-01-13 12:26 ` David Hildenbrand
2025-01-10 18:21 ` [PATCH v1 4/6] mm/hugetlb: rename folio_putback_active_hugetlb() to folio_putback_hugetlb() David Hildenbrand
2025-01-13 12:27 ` Baolin Wang
2025-01-10 18:21 ` [PATCH v1 5/6] mm/hugetlb-cgroup: convert hugetlb_cgroup_css_offline() to work on folios David Hildenbrand
2025-01-10 18:45 ` Matthew Wilcox
2025-01-10 18:21 ` [PATCH v1 6/6] mm/hugetlb: use folio->lru int demote_free_hugetlb_folios() David Hildenbrand
2025-01-10 18:59 ` Matthew Wilcox
2025-01-10 19:32 ` David Hildenbrand
2025-01-10 18:23 ` [PATCH v1 0/6] mm/hugetlb: folio and migration cleanups David Hildenbrand
2025-01-10 18:59 ` Matthew Wilcox
2025-01-10 19:17 ` David Hildenbrand
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=20250110182149.746551-2-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=willy@infradead.org \
/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