From: Matthew Wilcox <willy@infradead.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: David Hildenbrand <david@redhat.com>,
Barry Song <21cnbao@gmail.com>,
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, 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 17:34:53 +0000 [thread overview]
Message-ID: <ZgRYvQYmzLXfOlNK@casper.infradead.org> (raw)
In-Reply-To: <775d6fb4-f555-4edc-a3c2-2f5cfde3d9b6@arm.com>
On Wed, Mar 27, 2024 at 03:15:33PM +0000, Ryan Roberts wrote:
> >>> 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
>
> Also, I wouldn't want to hold this patch up in order to do this extra work. I
> think the 2 things are orthogonal? (supporting THP swap with MTE vs not using
> tail page flags for MTE). Can we discuss and handle it separately?
Yes, I'm not trying to hold this patch hostage.
next prev parent reply other threads:[~2024-03-27 17:35 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
2024-03-27 15:13 ` Ryan Roberts
2024-03-27 15:15 ` Ryan Roberts
2024-03-27 17:34 ` Matthew Wilcox [this message]
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=ZgRYvQYmzLXfOlNK@casper.infradead.org \
--to=willy@infradead.org \
--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=david@redhat.com \
--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=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).