From: Pedro Falcato <pedro.falcato@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
oliver.sang@intel.com, torvalds@linux-foundation.org,
jeffxu@google.com, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH v2 0/6] mm: Optimize mseal checks
Date: Fri, 9 Aug 2024 01:34:37 +0100 [thread overview]
Message-ID: <CAKbZUD0_BSv6KOgaRuqjLWGnttzcprcUu5WysSZeX8FXAvui5w@mail.gmail.com> (raw)
In-Reply-To: <20240808161226.b853642c0ecf530b5cef2ecc@linux-foundation.org>
On Fri, Aug 9, 2024 at 12:12 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed, 7 Aug 2024 22:13:03 +0100 Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
> > This series also depends on (and will eventually very slightly conflict with)
> > the powerpc series that removes arch_unmap[2].
>
> That's awkward. Please describe the dependency?
One of the transformations done in this patch series (patch 2) assumes
that arch_unmap either doesn't exist or does nothing.
PPC is the only architecture with an arch_unmap implementation, and
through the series I linked they're going to make it work via
->close().
What's the easiest way to deal with this? Can the PPC series go
through the mm tree?
I could also possibly work around this on my end, and either limit the
terribleness to the ppc arch_unmap code or limit the effectiveness of
the patch set a bit. But both of these options feel like somewhat
fighting the inevitable.
What do you think?
Thanks,
Pedro
next prev parent reply other threads:[~2024-08-09 0:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240807211309.2729719-1-pedro.falcato@gmail.com>
2024-08-08 23:12 ` Andrew Morton
2024-08-09 0:34 ` Pedro Falcato [this message]
2024-08-09 1:02 ` Jeff Xu
2024-08-09 19:34 ` Liam R. Howlett
2024-08-15 22:10 ` Jeff Xu
2024-08-16 1:58 ` Pedro Falcato
2024-08-16 17:07 ` Jeff Xu
2024-08-16 18:09 ` Pedro Falcato
2024-08-16 18:20 ` Jeff Xu
2024-08-16 18:26 ` Pedro Falcato
2024-08-16 18:42 ` Jeff Xu
2024-08-16 17:30 ` Jeff Xu
[not found] ` <20240807211309.2729719-2-pedro.falcato@gmail.com>
2024-08-09 9:57 ` [PATCH v2 1/6] mm: Move can_modify_vma to mm/internal.h Lorenzo Stoakes
[not found] ` <20240807211309.2729719-5-pedro.falcato@gmail.com>
2024-08-09 16:05 ` [PATCH v2 4/6] mm/mremap: Replace can_modify_mm with can_modify_vma Liam R. Howlett
2024-08-09 18:45 ` Pedro Falcato
2024-08-12 15:22 ` Liam R. Howlett
[not found] ` <20240807211309.2729719-3-pedro.falcato@gmail.com>
2024-08-09 16:15 ` [PATCH v2 2/6] mm/munmap: " Liam R. Howlett
2024-08-09 16:48 ` Liam R. Howlett
2024-08-09 18:53 ` Pedro Falcato
2024-08-09 19:24 ` Liam R. Howlett
2024-08-12 14:30 ` Jeff Xu
2024-08-12 16:57 ` Liam R. Howlett
2024-08-12 17:38 ` Jeff Xu
2024-08-12 19:25 ` Liam R. Howlett
[not found] ` <20240807211309.2729719-6-pedro.falcato@gmail.com>
2024-08-09 16:27 ` [PATCH v2 5/6] mseal: Replace can_modify_mm_madv with a vma variant Liam R. Howlett
2024-08-15 21:11 ` [PATCH v2 0/6] mm: Optimize mseal checks Jeff Xu
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=CAKbZUD0_BSv6KOgaRuqjLWGnttzcprcUu5WysSZeX8FXAvui5w@mail.gmail.com \
--to=pedro.falcato@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jeffxu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=oliver.sang@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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