From: Yang Shi <yang@os.amperecomputing.com>
To: David Hildenbrand <david@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: muchun.song@linux.dev, will@kernel.org,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hugetlbfs: add MTE support
Date: Tue, 2 Jul 2024 17:20:41 -0700 [thread overview]
Message-ID: <9dd065aa-f377-4b4c-893a-df69c9f67360@os.amperecomputing.com> (raw)
In-Reply-To: <fcf036e1-d65c-4a4b-9280-19024bb4da1b@redhat.com>
On 7/2/24 6:09 AM, David Hildenbrand wrote:
> On 02.07.24 14:34, Catalin Marinas wrote:
>> On Tue, Jun 25, 2024 at 04:37:17PM -0700, Yang Shi wrote:
>>> MTE can be supported on ram based filesystem. It is supported on tmpfs.
>>> There is use case to use MTE on hugetlbfs as well, adding MTE support.
>>>
>>> Signed-off-by: Yang Shi <yang@os.amperecomputing.com>
>>> ---
>>> fs/hugetlbfs/inode.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
>>> index ecad73a4f713..c34faef62daf 100644
>>> --- a/fs/hugetlbfs/inode.c
>>> +++ b/fs/hugetlbfs/inode.c
>>> @@ -110,7 +110,7 @@ static int hugetlbfs_file_mmap(struct file
>>> *file, struct vm_area_struct *vma)
>>> * way when do_mmap unwinds (may be important on powerpc
>>> * and ia64).
>>> */
>>> - vm_flags_set(vma, VM_HUGETLB | VM_DONTEXPAND);
>>> + vm_flags_set(vma, VM_HUGETLB | VM_DONTEXPAND | VM_MTE_ALLOWED);
>>> vma->vm_ops = &hugetlb_vm_ops;
>>
>> Last time I checked, about a year ago, this was not sufficient. One
>> issue is that there's no arch_clear_hugetlb_flags() implemented by your
>> patch, leaving PG_arch_{2,3} set on a page. The other issue was that I
>> initially tried to do this only on the head page but this did not go
>> well with the folio_copy() -> copy_highpage() which expects the
>> PG_arch_* flags on each individual page. The alternative was for
>> arch_clear_hugetlb_flags() to iterate over all the pages in a folio.
>
> This would likely also add a blocker for
> ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP on arm64 (no idea if there are now
> ways to move forward with that now, or if we are still not sure if we
> can actually add support), correct?
IIUC, it is not. We just need to guarantee each subpage has
PG_mte_tagged flag and allocated tags. The HVO just maps the 7 vmemmap
pages for sub pages to the first page, they still see the flag and the
space for tag is not impacted, right? Did I miss something?
>
>
next prev parent reply other threads:[~2024-07-03 0:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 23:37 Yang Shi
2024-06-26 20:40 ` Andrew Morton
2024-06-26 20:45 ` Yang Shi
2024-06-26 23:43 ` Yang Shi
2024-07-02 12:34 ` Catalin Marinas
2024-07-02 13:09 ` David Hildenbrand
2024-07-03 0:20 ` Yang Shi [this message]
2024-07-03 10:24 ` David Hildenbrand
2024-07-03 13:57 ` Catalin Marinas
2024-07-03 0:04 ` Yang Shi
2024-07-03 0:15 ` Yang Shi
2024-07-04 13:44 ` Catalin Marinas
2024-07-09 17:42 ` Yang Shi
2024-08-13 17:08 ` Yang Shi
2024-08-15 10:31 ` Catalin Marinas
2024-08-15 19:15 ` Yang Shi
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=9dd065aa-f377-4b4c-893a-df69c9f67360@os.amperecomputing.com \
--to=yang@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--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