From: Pengyu Zhang <zpenya1314@gmail.com>
To: corbet@lwn.net
Cc: rppt@kernel.org, linus.walleij@linaro.org,
fmdefrancesco@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Pengyu Zhang <zpenya1314@gmail.com>
Subject: [PATCH v1] Docs/mm: Fix a mistakes for pfn in page_tables.rst
Date: Wed, 9 Oct 2024 00:10:50 +0800 [thread overview]
Message-ID: <20241008161050.14732-1-zpenya1314@gmail.com> (raw)
The documentation incorrectly calculate the pfn value as 0x3fffff,
which should be 0x3ffff instead.It is obtained by right-shifting
0xffffc000 by 14 bits.
This patch corrects the value to prevent any potential confusion
for developers referencing this document.
Signed-off-by: Pengyu Zhang <zpenya1314@gmail.com>
---
Documentation/mm/page_tables.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/mm/page_tables.rst b/Documentation/mm/page_tables.rst
index be47b192a596..e7c69cc32493 100644
--- a/Documentation/mm/page_tables.rst
+++ b/Documentation/mm/page_tables.rst
@@ -29,7 +29,7 @@ address.
With a page granularity of 4KB and a address range of 32 bits, pfn 0 is at
address 0x00000000, pfn 1 is at address 0x00001000, pfn 2 is at 0x00002000
and so on until we reach pfn 0xfffff at 0xfffff000. With 16KB pages pfs are
-at 0x00004000, 0x00008000 ... 0xffffc000 and pfn goes from 0 to 0x3fffff.
+at 0x00004000, 0x00008000 ... 0xffffc000 and pfn goes from 0 to 0x3ffff.
As you can see, with 4KB pages the page base address uses bits 12-31 of the
address, and this is why `PAGE_SHIFT` in this case is defined as 12 and
--
2.25.1
next reply other threads:[~2024-10-08 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 16:10 Pengyu Zhang [this message]
2024-10-08 16:18 ` Mike Rapoport
2024-10-08 16:25 ` Zenghui Yu
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=20241008161050.14732-1-zpenya1314@gmail.com \
--to=zpenya1314@gmail.com \
--cc=corbet@lwn.net \
--cc=fmdefrancesco@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@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®