From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org
Cc: borntraeger@de.ibm.com, benh@kernel.crashing.org
Subject: [patch 0/6] s390 page tables on steroids ..
Date: Thu, 25 Oct 2007 20:15:20 +0200 [thread overview]
Message-ID: <20071025181520.880272069@de.ibm.com> (raw)
Greetings,
this patch series of six patches contains three mm related changes
for the s390 architecture:
i) 1K/2K page tables. With this patch set the cheating with the
pmd_t on s390 stops. So far a pmd contained 2/4 pointers instead
of just one which would be correct from an architectural stand
point. The Trouble with this is that it requires two common code
changes to make sub-page page tables possible. This features
is an important requirement for the kvm support on s390.
ii) Support for 4 levels of page tables. The address space limit for
64 bit processes is now 2^53. That should be enough for anyone ?
iii) Support for different number of page table levels. The limit
of 2^53 is nice but it slows down the tlb lookup that now has
to walk 4 instead of 3 levels. Patch #5 make the number of page
table levels dependent on the highest address a process is using.
If an mmap is done that raises the limit to the next level, the
page table gets another level. A downgrade is only done at process
start, so that 31 bit processes get a two level page table. A
normal 64 bit process starts with three levels.
The first three patches in the series contain the common code changes
that are needed to get all of this done. I did my best to find all the
place in the different architectures that need to be updated after the
common code changed. Please let me know if you find a place I missed.
The patches are against Linus's git tree.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2007-10-25 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 18:15 Martin Schwidefsky [this message]
2007-10-25 18:15 ` [patch 1/6] add mm argument to pte/pmd/pud/pgd_free Martin Schwidefsky, Benjamin Herrenschmidt, Martin Schwidefsky
2007-10-25 18:15 ` [patch 2/6] CONFIG_HIGHPTE vs. sub-page page tables Martin Schwidefsky, Martin Schwidefsky
2007-10-25 20:47 ` Benjamin Herrenschmidt
2007-10-26 7:42 ` Martin Schwidefsky
2007-10-26 8:00 ` Benjamin Herrenschmidt
2007-10-26 8:08 ` Martin Schwidefsky
2007-10-26 8:06 ` Martin Schwidefsky
2007-10-25 18:15 ` [patch 3/6] arch_update_pgd call Martin Schwidefsky, Martin Schwidefsky
2007-10-25 20:48 ` Benjamin Herrenschmidt
2007-10-25 22:49 ` Benjamin Herrenschmidt
2007-10-26 7:40 ` Martin Schwidefsky
2007-10-26 7:59 ` Benjamin Herrenschmidt
2007-10-26 8:22 ` Martin Schwidefsky
2007-10-26 11:28 ` Benjamin Herrenschmidt
2007-10-25 18:15 ` [patch 4/6] s390: 1K/2K page table pages Martin Schwidefsky, Martin Schwidefsky
2007-10-25 18:15 ` [patch 5/6] s390: Add four level page tables for CONFIG_64BIT=y Martin Schwidefsky, Martin Schwidefsky
2007-10-25 18:15 ` [patch 6/6] s390: dynamic page tables Martin Schwidefsky, Martin Schwidefsky
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=20071025181520.880272069@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.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;
as well as URLs for NNTP newsgroup(s).