From: James Houghton <jthoughton@google.com>
To: muchun.song@linux.dev
Cc: akpm@linux-foundation.org, catalin.marinas@arm.com,
david@kernel.org, fvdl@google.com, jthoughton@google.com,
linu.cherian@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mark.rutland@arm.com, nikos.nikoleris@arm.com,
osalvador@suse.de, rientjes@google.com, ryan.roberts@arm.com,
sunnanyong@huawei.com, will@kernel.org, yuzhao@google.com
Subject: Re: [PATCH v2 01/20] hugetlb: Don't restore vmemmap of non-HVOed folios on bulk restore error
Date: Wed, 21 Oct 2026 21:27:37 +0000 [thread overview]
Message-ID: <20261021212738.321547-1-jthoughton@google.com> (raw)
In-Reply-To: <491B482A-8177-447A-8CDB-AF83C13A5DEE@linux.dev>
On Wed, Oct 21, 2026 at 2:33 AM Muchun Song <muchun.song@linux.dev> wrote:
> > On Oct 3, 2026, at 08:21, James Houghton <jthoughton@google.com> wrote:
> > diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> > index a1b51251103b..4dac7ed1df57 100644
> > --- a/mm/hugetlb.c
> > +++ b/mm/hugetlb.c
> > @@ -1613,9 +1613,14 @@ static void bulk_vmemmap_restore_error(struct hstate *h,
> > * page is made a surplus page and removed from the list.
> > * If are able to restore vmemmap and free one hugetlb page, we
> > * quit processing the list to retry the bulk operation.
> > + *
> > + * Folios whose vmemmap was never optimized (e.g. because HVO
> > + * failed when they were allocated) can be freed right away;
> > + * remove_hugetlb_folio() has already cleared their hugetlb flag.
>
> Since you mentioned the hugetlb flag is cleared. So it's unnecessary to clear it again.
>
> > */
> > list_for_each_entry_safe(folio, t_folio, folio_list, lru)
> > - if (hugetlb_vmemmap_restore_folio(h, folio)) {
> > + if (folio_test_hugetlb_vmemmap_optimized(folio) &&
> > + hugetlb_vmemmap_restore_folio(h, folio)) {
> > list_del(&folio->lru);
> > spin_lock_irq(&hugetlb_lock);
> > add_hugetlb_folio(h, folio, true);
>
> Something like following:
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 6a011b627986..1ab3e61f4704 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1616,21 +1616,31 @@ static void bulk_vmemmap_restore_error(struct hstate *h,
> * If are able to restore vmemmap and free one hugetlb page, we
> * quit processing the list to retry the bulk operation.
> */
> - list_for_each_entry_safe(folio, t_folio, folio_list, lru)
> - if (hugetlb_vmemmap_restore_folio(h, folio)) {
> - list_del(&folio->lru);
> + list_for_each_entry_safe(folio, t_folio, folio_list, lru) {
> + list_del(&folio->lru);
> +
> + /*
> + * remove_hugetlb_folio() already cleared the hugetlb flag
> + * for folios whose vmemmap was not optimized, so they can
> + * be freed without restoring vmemmap.
> + */
> + if (folio_test_hugetlb(folio) &&
> + hugetlb_vmemmap_restore_folio(h, folio)) {
> spin_lock_irq(&hugetlb_lock);
> add_hugetlb_folio(h, folio, true);
> spin_unlock_irq(&hugetlb_lock);
> - } else {
> - list_del(&folio->lru);
> + continue;
> + }
> +
> + if (folio_test_hugetlb(folio)) {
> spin_lock_irq(&hugetlb_lock);
> __folio_clear_hugetlb(folio);
> spin_unlock_irq(&hugetlb_lock);
> - update_and_free_hugetlb_folio(h, folio, false);
> - cond_resched();
> - break;
> }
> + update_and_free_hugetlb_folio(h, folio, false);
> + cond_resched();
> + break;
> + }
> }
> }
Thanks, Muchun. :) I think it's slightly easier to read without the second
folio_test_hugetlb(), like this:
list_for_each_entry_safe(folio, t_folio, folio_list, lru) {
list_del(&folio->lru);
/*
* remove_hugetlb_folio() already cleared the hugetlb flag
* for folios whose vmemmap was not optimized, so they can
* be freed without restoring vmemmap.
*/
if (folio_test_hugetlb(folio)) {
if (hugetlb_vmemmap_restore_folio(h, folio)) {
spin_lock_irq(&hugetlb_lock);
add_hugetlb_folio(h, folio, true);
spin_unlock_irq(&hugetlb_lock);
continue;
}
spin_lock_irq(&hugetlb_lock);
__folio_clear_hugetlb(folio);
spin_unlock_irq(&hugetlb_lock);
}
update_and_free_hugetlb_folio(h, folio, false);
cond_resched();
break;
}
Applied this in the v3.
next prev parent reply other threads:[~2026-10-21 21:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 0:21 [PATCH v2 00/20] Another attempt at HVO support on arm64 James Houghton
2026-10-03 0:21 ` [PATCH v2 01/20] hugetlb: Don't restore vmemmap of non-HVOed folios on bulk restore error James Houghton
2026-10-21 9:32 ` Muchun Song
2026-10-21 21:27 ` James Houghton [this message]
2026-10-03 0:21 ` [PATCH v2 02/20] arm64/pgtable: Clear AF with LDCLR on supported systems James Houghton
2026-10-03 0:21 ` [PATCH v2 03/20] hugetlb_vmemmap: Always flush TLB if needed upon PTE remapping James Houghton
2026-10-21 9:54 ` Muchun Song
2026-10-21 21:59 ` James Houghton
2026-10-03 0:21 ` [PATCH v2 04/20] hugetlb_vmemmap: Leave pages partially HVOed upon restore failure James Houghton
2026-10-03 0:21 ` [PATCH v2 05/20] hugetlb_vmemmap: Use try_update_vmemmap_pte to update in-use PTEs James Houghton
2026-10-03 0:21 ` [PATCH v2 06/20] hugetlb_vmemmap: Allow architectures to dynamically disallow HVO James Houghton
2026-10-03 0:21 ` [PATCH v2 07/20] hugetlb_vmemmap: Disable HVO sysctl if arch doesn't support HVO James Houghton
2026-10-03 0:21 ` [PATCH v2 08/20] hugetlb: Fully initialize tail struct pages of non-pre-HVOed bootmem folios James Houghton
2026-10-03 0:21 ` [PATCH v2 09/20] hugetlb_vmemmap: Allow architectures to make HVO enablement boot-time only James Houghton
2026-10-03 0:21 ` [PATCH v2 10/20] hugetlb_vmemmap: Expose whether HVO is enabled to architecture code James Houghton
2026-10-03 0:21 ` [PATCH v2 11/20] arm64: Add bbm_through_af capability James Houghton
2026-10-03 0:21 ` [PATCH v2 12/20] arm64: Implement try_update_vmemmap_pte using the AF trick James Houghton
2026-10-03 0:21 ` [PATCH v2 13/20] arm64: Support hugetlb vmemmap optimization James Houghton
2026-10-03 0:21 ` [PATCH v2 14/20] hugetlb_vmemmap: Add fault injection for in-place vmemmap PTE updates James Houghton
2026-10-03 0:21 ` [PATCH v2 15/20] selftests/mm: Add HugeTLB vmemmap optimization stress test James Houghton
2026-10-03 0:21 ` [PATCH v2 16/20 DO-NOT-MERGE] hugetlb_vmemmap: Use try_populate_vmemmap_pmd for replacing in-use PMDs James Houghton
2026-10-03 0:21 ` [PATCH v2 17/20 DO-NOT-MERGE] arm64: Implement try_populate_vmemmap_pmd using AF trick James Houghton
2026-10-03 0:21 ` [PATCH v2 18/20 DO-NOT-MERGE] arm64: Drop BBML3 requirement for HVO James Houghton
2026-10-03 0:21 ` [PATCH v2 19/20 DO-NOT-MERGE] hugetlb_vmemmap: Add fault injection for in-place vmemmap PMD splits James Houghton
2026-10-03 0:21 ` [PATCH v2 20/20 DO-NOT-MERGE] selftests/mm: Add HVO pmd-split fault injection tests James Houghton
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=20261021212738.321547-1-jthoughton@google.com \
--to=jthoughton@google.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=fvdl@google.com \
--cc=linu.cherian@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=muchun.song@linux.dev \
--cc=nikos.nikoleris@arm.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=sunnanyong@huawei.com \
--cc=will@kernel.org \
--cc=yuzhao@google.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
all inboxes | Powered by JetHome®