From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update MEMORY MAPPING section
Date: Thu, 12 Dec 2024 15:40:44 +0100 [thread overview]
Message-ID: <033e50f9-b85d-4b66-932b-ae21ca85b16e@redhat.com> (raw)
In-Reply-To: <20241211105315.21756-1-lorenzo.stoakes@oracle.com>
On 11.12.24 11:53, Lorenzo Stoakes wrote:
> Update the MEMORY MAPPING section to contain VMA logic as it makes no
> sense to have these two sections separate.
>
> Additionally, add files which permit changes to the attributes and/or
> ranges spanned by memory mappings, in essence anything which might alter
> the output of /proc/$pid/[s]maps.
>
> This is necessarily fuzzy, as there is not quite as good separation of
> concerns as we would ideally like in the kernel. However each of these
> files interacts with the VMA and memory mapping logic in such a way as to
> be inseparatable from it, and it is important that they are maintained in
> conjunction with it.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
LGTM, thanks!
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-12-12 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:53 Lorenzo Stoakes
2024-12-11 18:36 ` Jeff Xu
2024-12-11 18:57 ` Lorenzo Stoakes
2024-12-13 5:50 ` Yu Zhao
2024-12-13 8:25 ` Vlastimil Babka
2024-12-13 9:00 ` Yu Zhao
2024-12-13 9:10 ` Vlastimil Babka
2024-12-13 9:17 ` Lorenzo Stoakes
2024-12-13 9:23 ` Lorenzo Stoakes
2024-12-13 9:36 ` Yu Zhao
2024-12-13 15:05 ` Jeff Xu
2024-12-13 15:19 ` Lorenzo Stoakes
2024-12-12 8:09 ` Vlastimil Babka
2024-12-12 14:40 ` David Hildenbrand [this message]
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=033e50f9-b85d-4b66-932b-ae21ca85b16e@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--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