From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
"Liam R. Howlett" <liam@infradead.org>,
Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@kernel.org>,
linux-arch@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] docs/mm: describe set_memory() and set_direct_map() APIs
Date: Wed, 9 Sep 2026 15:49:48 +0200 [thread overview]
Message-ID: <7e4a9b02-4346-4526-953c-2a1f2eea87d2@kernel.org> (raw)
In-Reply-To: <aqE4hFXS0YHZKLEy@kernel.org>
On 9/9/26 12:44, Mike Rapoport wrote:
> On Wed, Sep 09, 2026 at 12:30:01PM +0200, David Hildenbrand (Arm) wrote:
>> On 9/9/26 11:45, Mike Rapoport (Microsoft) wrote:
>>> The set_memory() and set_direct_map() APIs change permissions of existing
>>> kernel mappings, but their semantics are only described by the code, and
>>> that code differs from architecture to architecture.
>>>
>>> Add Documentation/mm/kernel-page-tables.rst that briefly describes what the
>>> kernel page tables consist of, defines the semantics both APIs have in
>>> common, including the parts that are easy to get wrong, and lists the
>>> differences between the architecture implementations.
>>>
>>> Add kernel-doc comments for the generic set_memory() and set_direct_map()
>>> stubs and link them into Documentation/core-api/mm-api.rst.
>>>
>>> Assisted-by: copilot:claude-opus
>>> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>>> ---
>>> The semantics of set_memory() and set_direct_map() are currently described
>>> only by the code, and the code differs from architecture to architecture.
>>>
>>> Document what these APIs actually promise, what they merely hint at, and how
>>> the architectures disagree.
>>>
>>> The discussions that prompted this:
>>>
>>> https://lore.kernel.org/all/a98df077-3e97-4eea-8bfe-470bad9ff9e0@kernel.org
>>> https://lore.kernel.org/all/5026dbec-0b71-4408-a78a-484a4b8e77dd@intel.com
>>> ---
>>> Documentation/core-api/mm-api.rst | 9 +
>>> Documentation/mm/index.rst | 1 +
>>> Documentation/mm/kernel-page-tables.rst | 402 ++++++++++++++++++++++++++++++++
>>
>> Before I read any of this, how much did you review and edit whatever the LLM
>> came up with?
>
> I never send something I don't like :)
Good. The rather excessive doc patch arrived rather fast so I had to ask :)
--
Cheers,
David
prev parent reply other threads:[~2026-09-09 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 9:45 Mike Rapoport (Microsoft)
2026-09-09 10:30 ` David Hildenbrand (Arm)
2026-09-09 10:44 ` Mike Rapoport
2026-09-09 13:49 ` David Hildenbrand (Arm) [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=7e4a9b02-4346-4526-953c-2a1f2eea87d2@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=liam@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®