From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>, Barry Song <21cnbao@gmail.com>
Cc: catalin.marinas@arm.com, will@kernel.org,
akpm@linux-foundation.org, hughd@google.com, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org, chrisl@kernel.org,
mark.rutland@arm.com, ryan.roberts@arm.com, steven.price@arm.com,
Barry Song <v-songbaohua@oppo.com>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Peter Collingbourne <pcc@google.com>,
Yosry Ahmed <yosryahmed@google.com>, Peter Xu <peterx@redhat.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH 1/1] arm64: mm: swap: support THP_SWAP on hardware with MTE
Date: Wed, 27 Mar 2024 15:57:37 +0100 [thread overview]
Message-ID: <1006392c-c437-46c0-9a2e-e25e52236b67@redhat.com> (raw)
In-Reply-To: <ZgQy24OJqkILGRSO@casper.infradead.org>
On 27.03.24 15:53, Matthew Wilcox wrote:
> On Sat, Mar 23, 2024 at 12:41:36AM +1300, Barry Song wrote:
>> Commit d0637c505f8a1 ("arm64: enable THP_SWAP for arm64") brings up
>> THP_SWAP on ARM64, but it doesn't enable THP_SWP on hardware with
>> MTE as the MTE code works with the assumption tags save/restore is
>> always handling a folio with only one page.
>>
>> The limitation should be removed as more and more ARM64 SoCs have
>> this feature. Co-existence of MTE and THP_SWAP becomes more and
>> more important.
>>
>> This patch makes MTE tags saving support large folios, then we don't
>> need to split large folios into base pages for swapping out on ARM64
>> SoCs with MTE any more.
>
> Can we go further than this patch and only support PG_mte_tagged and
> PG_mte_lock on folio->flags instead of page->flags? We're down to using
I think we discussed that already and what I learned is that it "gets a
bit complicated". But I'm hoping we can get that discussion started again.
> page->flags for these two MTE bits, a whole lot of s390 junk, PG_hwpoison,
> PG_head, PG_anon_exclusive and Zone/Section/Node/KASAN/last_cpupid.
... just like PG_anon_exclusive "gets a bit complicated". Well, I think
I might have finally found a way to make it work, I'll only have to
uglify fork() a bit.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-03-27 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:41 [PATCH 0/1] THP_SWAP support for ARM64 SoC with MTE Barry Song
2024-03-22 11:41 ` [PATCH 1/1] arm64: mm: swap: support THP_SWAP on hardware " Barry Song
2024-03-26 17:37 ` Ryan Roberts
2024-03-27 12:23 ` Catalin Marinas
2024-03-27 14:53 ` Matthew Wilcox
2024-03-27 14:57 ` David Hildenbrand [this message]
2024-03-27 15:13 ` Ryan Roberts
2024-03-27 15:15 ` Ryan Roberts
2024-03-27 17:34 ` Matthew Wilcox
2024-03-27 17:58 ` Catalin Marinas
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=1006392c-c437-46c0-9a2e-e25e52236b67@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=chrisl@kernel.org \
--cc=hughd@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pcc@google.com \
--cc=peterx@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shikemeng@huaweicloud.com \
--cc=steven.price@arm.com \
--cc=v-songbaohua@oppo.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yosryahmed@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;
as well as URLs for NNTP newsgroup(s).