From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Huang Ying <ying.huang@linux.alibaba.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Yang Shi <yang@os.amperecomputing.com>,
"Christoph Lameter (Ampere)" <cl@gentwo.org>,
Dev Jain <dev.jain@arm.com>, Barry Song <baohua@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Yicong Yang <yangyicong@hisilicon.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Yin Fengwei <fengwei_yin@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH -v2 1/2] mm: add spurious fault fixing support for huge pmd
Date: Tue, 14 Oct 2025 16:38:05 +0200 [thread overview]
Message-ID: <2861a35d-4f8e-4ee1-bd11-b915580c9ce3@redhat.com> (raw)
In-Reply-To: <4c453dcc-2837-4f1a-905b-3462270f5e31@lucifer.local>
>
> /* Skip spurious TLB flush for retried page fault */
> if (vmf->flags & FAULT_FLAG_TRIED)
> goto unlock;
> /*
> * This is needed only for protection faults but the arch code
> * is not yet telling us if this is a protection fault or not.
> * This still avoids useless tlb flushes for .text page faults
> * with threads.
> */
> if (vmf->flags & FAULT_FLAG_WRITE)
> flush_tlb_fix_spurious_fault(vmf->vma, vmf->address,
> vmf->pte);
>
>
> So I don't see why it's so egregious to have the equivalent here, or actually
> ideally to abstract the code entirely.
Let's definitely not duplicate such comments whereby one instance will
end up bitrotting.
When talking about spurious faults I assume the educated reader will
usually find the right comments -- like you easily did :P
However I agree that ...
>
> In commit b22cc9a9c7ff ("mm/rmap: convert "enum rmap_level" to "enum
> pgtable_level"") David introduced:
>
> enum pgtable_level {
> PGTABLE_LEVEL_PTE = 0,
> PGTABLE_LEVEL_PMD,
> PGTABLE_LEVEL_PUD,
> PGTABLE_LEVEL_P4D,
> PGTABLE_LEVEL_PGD,
> };
>
> Which allows for sensible abstraction.
... if there is an easier way to just unify the code and have the
comments at a central place, even better.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-10-14 14:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:20 [PATCH -v2 0/2] arm, tlbflush: avoid TLBI broadcast if page reused in write fault Huang Ying
2025-10-13 9:20 ` [PATCH -v2 1/2] mm: add spurious fault fixing support for huge pmd Huang Ying
2025-10-14 14:21 ` Lorenzo Stoakes
2025-10-14 14:38 ` David Hildenbrand [this message]
2025-10-14 14:49 ` Lorenzo Stoakes
2025-10-14 14:58 ` David Hildenbrand
2025-10-14 15:13 ` Lorenzo Stoakes
2025-10-15 8:43 ` Huang, Ying
2025-10-15 11:20 ` Lorenzo Stoakes
2025-10-15 12:23 ` David Hildenbrand
2025-10-16 2:22 ` Huang, Ying
2025-10-16 8:25 ` Lorenzo Stoakes
2025-10-16 8:59 ` David Hildenbrand
2025-10-16 9:12 ` Huang, Ying
2025-10-13 9:20 ` [PATCH -v2 2/2] arm64, tlbflush: don't TLBI broadcast if page reused in write fault Huang Ying
2025-10-15 15:28 ` Ryan Roberts
2025-10-16 1:35 ` Huang, Ying
2025-10-22 4:08 ` Barry Song
2025-10-22 7:31 ` Huang, Ying
2025-10-22 8:14 ` Barry Song
2025-10-22 9:02 ` Huang, Ying
2025-10-22 9:17 ` Barry Song
2025-10-22 9:30 ` Huang, Ying
2025-10-22 9:37 ` Barry Song
2025-10-22 9:46 ` Huang, Ying
2025-10-22 9:55 ` Barry Song
2025-10-22 10:22 ` Barry Song
2025-10-22 10:34 ` Huang, Ying
2025-10-22 10:52 ` Barry Song
2025-10-23 1:22 ` Huang, Ying
2025-10-23 5:39 ` Barry Song
2025-10-23 6:15 ` Huang, Ying
2025-10-23 10:18 ` Ryan Roberts
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=2861a35d-4f8e-4ee1-bd11-b915580c9ce3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=dev.jain@arm.com \
--cc=fengwei_yin@linux.alibaba.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=yangyicong@hisilicon.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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