From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>, <linux-mm@kvack.org>,
<linux-arm-kernel@lists.infradead.org>,
Will Deacon <will@kernel.org>, <Aishwarya.TCV@arm.com>
Subject: Re: [PATCH] mm/huge_memory: Initialise the tags of the huge zero folio
Date: Tue, 4 Nov 2025 00:59:33 +0530 [thread overview]
Message-ID: <a281af74-99cf-49e2-99c5-290bdb84ebd0@ti.com> (raw)
In-Reply-To: <aQjRa-Bh8J8Smgur@arm.com>
On 11/3/2025 9:29 PM, Catalin Marinas wrote:
> On Mon, Nov 03, 2025 at 03:41:03PM +0100, David Hildenbrand (Red Hat) wrote:
>>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>>> index d816ff44faff..125dfa6c613b 100644
>>> --- a/arch/arm64/mm/fault.c
>>> +++ b/arch/arm64/mm/fault.c
>>> @@ -969,6 +969,16 @@ struct folio *vma_alloc_zeroed_movable_folio(struct vm_area_struct *vma,
>>> void tag_clear_highpage(struct page *page)
>>> {
>>> + /*
>>> + * Check if MTE is supported and fall back to clear_highpage().
>>> + * get_huge_zero_folio() unconditionally passes __GFP_ZEROTAGS and
>>> + * post_alloc_hook() will invoke tag_clear_highpage().
>>> + */
>>> + if (!system_supports_mte()) {
>>> + clear_highpage(page);
>>> + return;
>>> + }
>> LGTM!
> I tested it with and without MTE and it works fine.
I tested the above patch on ARM64 based TI J7200 EVM board.
Boots fine. Feel free to use my T/B:
Tested-by: Beleswar Padhi <b-padhi@ti.com>
Thanks,
Beleswar
>
> Andrew, would you like a separate patch or are you ok with folding this
> into the previous patch?
>
> Thanks.
>
next prev parent reply other threads:[~2025-11-03 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 16:57 Catalin Marinas
2025-10-31 17:15 ` David Hildenbrand
2025-11-03 13:32 ` Mark Brown
2025-11-03 14:30 ` Catalin Marinas
2025-11-03 14:41 ` David Hildenbrand (Red Hat)
2025-11-03 15:59 ` Catalin Marinas
2025-11-03 19:29 ` Beleswar Prasad Padhi [this message]
2025-11-04 1:05 ` Andrew Morton
2025-11-04 8:52 ` Catalin Marinas
2025-11-04 11:53 ` [PATCH] mm/huge_memory: Initialise the tags of the huge zero Lance Yang
2025-11-08 19:19 ` [PATCH] mm/huge_memory: initialise the tags of the huge zero folio Jan Polensky
2025-11-09 0:42 ` [PATCH] Clarification: please ignore earlier submission Jan Polensky
2025-11-09 0:36 ` [PATCH] mm/huge_memory: restrict __GFP_ZEROTAGS to HW tagging architectures Jan Polensky
2025-11-10 9:09 ` David Hildenbrand (Red Hat)
2025-11-10 9:48 ` Jan Polensky
2025-11-10 9:53 ` David Hildenbrand (Red Hat)
2025-11-10 15:28 ` Catalin Marinas
2025-11-10 15:55 ` Catalin Marinas
2025-11-22 12:04 ` Balbir Singh
2025-11-24 10:57 ` David Hildenbrand (Red Hat)
2025-11-24 18:08 ` Andrew Morton
2025-11-11 10:44 ` Jan Polensky
2025-11-11 12:27 ` David Hildenbrand (Red Hat)
2025-11-11 12:28 ` David Hildenbrand (Red Hat)
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=a281af74-99cf-49e2-99c5-290bdb84ebd0@ti.com \
--to=b-padhi@ti.com \
--cc=Aishwarya.TCV@arm.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=will@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