From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@kernel.org>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Ira Weiny <ira.weiny@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v3] Documentation/page_tables: Add info about MMU/TLB and Page Faults
Date: Tue, 03 Oct 2023 10:01:09 -0600 [thread overview]
Message-ID: <87h6n7elve.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230904180111.GG3223@kernel.org>
Mike Rapoport <rppt@kernel.org> writes:
> On Fri, Aug 18, 2023 at 01:19:34PM +0200, Fabio M. De Francesco wrote:
>> Extend page_tables.rst by adding a section about the role of MMU and TLB
>> in translating between virtual addresses and physical page frames.
>> Furthermore explain the concept behind Page Faults and how the Linux
>> kernel handles TLB misses. Finally briefly explain how and why to disable
>> the page faults handler.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Ira Weiny <ira.weiny@intel.com>
>> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> Cc: Matthew Wilcox <willy@infradead.org>
>> Cc: Mike Rapoport <rppt@kernel.org>
>> Cc: Randy Dunlap <rdunlap@infradead.org>
>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
>
> Acked-by: Mike Rapoport (IBM) <rppt@kernel.org>
I've applied this, thanks; sorry for the delay,
jon
prev parent reply other threads:[~2023-10-03 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:19 Fabio M. De Francesco
2023-09-04 18:01 ` Mike Rapoport
2023-10-03 16:01 ` Jonathan Corbet [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=87h6n7elve.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.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