From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH v1 1/4] mm: move vma_kernel_pagesize() from hugetlb to mm.h
Date: Mon, 9 Mar 2026 14:47:03 +0100 [thread overview]
Message-ID: <edd058dc-9d94-4c5d-a2b1-245a04b54eb0@kernel.org> (raw)
In-Reply-To: <d8cdf99b-3139-49b5-bc4f-dda139856021@lucifer.local>
On 3/9/26 14:41, Lorenzo Stoakes (Oracle) wrote:
> On Fri, Mar 06, 2026 at 02:25:51PM +0100, David Hildenbrand (Arm) wrote:
>> On 3/6/26 12:07, Lorenzo Stoakes (Oracle) wrote:
>>>
>>> LGTM, but you need to fix up VMA tests, I attach a patch below to do this. Will
>>> this resolved:
>>
>> Thanks!
>>
>> I assume that should go into patch #2 instead?
>>
>>>
>>> Reviewed-by: Lorenzo Stoakes (Oracle) <ljs@kernel.org>
>>
>>
>> [...]
>>
>>> ---
>>> tools/testing/vma/include/dup.h | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/tools/testing/vma/include/dup.h b/tools/testing/vma/include/dup.h
>>> index 3078ff1487d3..65b1030a7fdf 100644
>>> --- a/tools/testing/vma/include/dup.h
>>> +++ b/tools/testing/vma/include/dup.h
>>> @@ -1318,3 +1318,10 @@ static inline void vma_set_file(struct vm_area_struct *vma, struct file *file)
>>> swap(vma->vm_file, file);
>>> fput(file);
>>> }
>>> +
>>> +static inline unsigned long vma_kernel_pagesize(struct vm_area_struct *vma)
>>> +{
>>> + if (unlikely(vma->vm_ops && vma->vm_ops->pagesize))
>>> + return vma->vm_ops->pagesize(vma);
>>> + return PAGE_SIZE;
>>
>> Should we just KIS and use PAGE_SIZE for the test?
>
> Yeah that's fine, but then should go in tools/testing/vma/include/custom.h :>)
I'll place it in there, then, thanks.
--
Cheers,
David
next prev parent reply other threads:[~2026-03-09 13:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 10:15 [PATCH v1 0/4] mm: move vma_(kernel|mmu)_pagesize() out of hugetlb.c David Hildenbrand (Arm)
2026-03-06 10:15 ` [PATCH v1 1/4] mm: move vma_kernel_pagesize() from hugetlb to mm.h David Hildenbrand (Arm)
2026-03-06 11:07 ` Lorenzo Stoakes (Oracle)
2026-03-06 13:25 ` David Hildenbrand (Arm)
2026-03-09 13:41 ` Lorenzo Stoakes (Oracle)
2026-03-09 13:47 ` David Hildenbrand (Arm) [this message]
2026-03-09 13:44 ` Lorenzo Stoakes (Oracle)
2026-03-06 10:15 ` [PATCH v1 2/4] mm: move vma_mmu_pagesize() from hugetlb to vma.c David Hildenbrand (Arm)
2026-03-06 11:11 ` Lorenzo Stoakes (Oracle)
2026-03-06 10:15 ` [PATCH v1 3/4] KVM: remove hugetlb.h inclusion David Hildenbrand (Arm)
2026-03-06 11:11 ` Lorenzo Stoakes (Oracle)
2026-03-06 13:27 ` David Hildenbrand (Arm)
2026-03-06 10:16 ` [PATCH v1 4/4] KVM: PPC: " David Hildenbrand (Arm)
2026-03-06 11:12 ` Lorenzo Stoakes (Oracle)
2026-03-06 11:13 ` [PATCH v1 0/4] mm: move vma_(kernel|mmu)_pagesize() out of hugetlb.c Pedro Falcato
2026-03-06 11:19 ` Lorenzo Stoakes (Oracle)
2026-03-06 13:12 ` David Hildenbrand (Arm)
2026-03-09 13:42 ` Lorenzo Stoakes (Oracle)
2026-03-09 15:07 ` David Hildenbrand (Arm)
2026-03-10 10:42 ` Vlastimil Babka
2026-03-06 15:30 ` Mike Rapoport
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=edd058dc-9d94-4c5d-a2b1-245a04b54eb0@kernel.org \
--to=david@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.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