From: Peter Watkins <treestem@gmail.com>
To: linux-mips@linux-mips.org
Cc: Ralf Baechle <ralf@linux-mips.org>
Subject: [PATCH] 64K page size
Date: Wed, 23 Aug 2006 11:15:49 -0400 [thread overview]
Message-ID: <44EC7125.7000000@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
Hello,
There are a number of changes required to support larger page sizes, but
this one I thought worth sending up right away.
The code in pgtable-64.h assumes TASK_SIZE is always bigger than a first
level PGDIR_SIZE. This is not the case for 64K pages, where task size is
40 bits (1TB) and a pgd entry can map 42 bits. This leads to
USER_PTRS_PER_PGD being zero for 64K pages.
If there is interest in other changes for 64K pages, I can send more.
Signed-off-by: Peter Watkins <treestem@gmail.com>
[-- Attachment #2: patch-userptrs-2.6.18-rc1.txt --]
[-- Type: text/plain, Size: 622 bytes --]
diff --git a/include/asm-mips/pgtable-64.h b/include/asm-mips/pgtable-64.h
index e3db932..9ce72bd 100644
--- a/include/asm-mips/pgtable-64.h
+++ b/include/asm-mips/pgtable-64.h
@@ -93,8 +93,12 @@ #define PTRS_PER_PGD ((PAGE_SIZE << PGD_
#define PTRS_PER_PMD ((PAGE_SIZE << PMD_ORDER) / sizeof(pmd_t))
#define PTRS_PER_PTE ((PAGE_SIZE << PTE_ORDER) / sizeof(pte_t))
+#if PGDIR_SIZE >= TASK_SIZE
+#define USER_PTRS_PER_PGD (1)
+#else
#define USER_PTRS_PER_PGD (TASK_SIZE / PGDIR_SIZE)
-#define FIRST_USER_ADDRESS 0
+#endif
+#define FIRST_USER_ADDRESS 0UL
#define VMALLOC_START MAP_BASE
#define VMALLOC_END \
next reply other threads:[~2006-08-23 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 15:15 Peter Watkins [this message]
2006-08-23 16:00 ` [PATCH] 64K page size Thiemo Seufer
2006-08-23 16:23 ` Jonathan Day
2006-08-23 17:53 ` Thiemo Seufer
2006-08-25 0:28 ` Ralf Baechle
2006-08-25 5:11 ` Jonathan Day
2006-08-29 14:07 ` Ralf Baechle
2006-08-31 3:48 ` Yoichi Yuasa
2006-08-31 21:24 ` Ralf Baechle
2006-08-29 13:50 ` Ralf Baechle
2006-08-31 15:12 ` Peter Watkins
2006-08-29 14:01 ` Ralf Baechle
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=44EC7125.7000000@gmail.com \
--to=treestem@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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