public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: 4level-2.6.9-1 released
Date: Tue, 19 Oct 2004 04:04:26 +0200	[thread overview]
Message-ID: <20041019020425.GA32393@wotan.suse.de> (raw)


I put a new version of the 4level page table patchkit at 

ftp://ftp.suse.com/pub/people/ak/4level/4level-2.6.9-1.gz

It extends the Linux VM to understand 4level page tables and extends
the virtual address room of each x86-64 process to be 128TB (previously
512GB) 

The extension is quite straight forward without any significant
redesign. The new level is called pml4.

The patch needs some simple changes to all architectures.

Changes compared to 4level-2.6.9rc4-2: 
- Merged with 2.6.9 (release, not -final) 
- Converted more architectures.

Porting status:
- i386   works with 2/3 levels.
- x86-64 works with 4 levels.
- ppc64  works with 3 levels
- ia64   works with 3 levels
- sh     converted, but was unable to compile because it's broken in mainline
- ppc32  converted, compiles, not tested.
- alpha  converted, boots
- sparc64 converted, compiles, not tested
- arm*/h8300/cris/m32r/m68k*/mips/parisc/s390/sh64/um/v850: still need to be converted
For many of them it's difficult because they don't even compile in mainline.

More testing on x86-64 and other architectures and new architecture ports would be 
appreciated. 

The changes needed to convert an architecture over are relatively simple, 
see the i386 port as an example.

-Andi


             reply	other threads:[~2004-10-19  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19  2:04 Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19 14:40 4level-2.6.9-1 released Mikael Pettersson

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=20041019020425.GA32393@wotan.suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@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