All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	x86@kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Beulich <jbeulich@novell.com>,
	Stable Kernel <stable@kernel.org>
Subject: Re: [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit
Date: Fri, 06 Jun 2008 08:59:24 +0100	[thread overview]
Message-ID: <4848EE5C.6040003@goop.org> (raw)
In-Reply-To: <87ve0ntk6v.fsf@basil.nowhere.org>

Andi Kleen wrote:
> Jeremy Fitzhardinge <jeremy@goop.org> writes:
>   
>> The 46-bit mask used in 64-bit seems pretty arbitrary. 
>>     
>
> The rationale for the 46 bits is that the kernel needs roughly 4x as 
> much virtual space as physical space and the virtual space is limited
> to 48bits.
>
> To be exact 47 bits is always user space and the 47 bits remaining
> for the kernel are split into half, with one half for the direct mapping
> and the other half for random mappings.  With some pushing you could
> extend it to 46.5 bits or so, but beyond that you'll be in trouble.
>   

Why's that?  Is the issue the amount of memory needed for pagetables and 
page structures if you did have more than 2^48 bytes of physical memory?

> It's not arbitrary at all.
I didn't say it was.  That was the introduction to my explanation of why 
I didn't think it was arbitrary.  Of course, if there had been a comment 
there explaining the rationale, I wouldn't have had to make one up...

    J

  parent reply	other threads:[~2008-06-06  8:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 15:21 [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit Jeremy Fitzhardinge
2008-06-05 15:34 ` Jan Beulich
2008-06-05 15:42   ` Jeremy Fitzhardinge
2008-06-05 16:45     ` H. Peter Anvin
2008-06-05 21:14       ` Jeremy Fitzhardinge
2008-06-07 18:35         ` H. Peter Anvin
2008-06-06  9:21   ` [PATCH UPDATED] x86: set PAE PHYSICAL_MASK_SHIFT to 44 bits Jeremy Fitzhardinge
2008-06-06  9:58     ` Jan Beulich
2008-06-06 13:15     ` Andi Kleen
2008-06-06 13:50       ` Jeremy Fitzhardinge
2008-06-10 10:31     ` Ingo Molnar
2008-06-10 13:06       ` Jeremy Fitzhardinge
2008-06-13  7:24         ` Ingo Molnar
2008-06-06  1:40 ` [PATCH] x86: set PAE PHYSICAL_MASK_SHIFT to match 64-bit Andi Kleen
2008-06-06  7:14   ` Jan Beulich
2008-06-06  7:59   ` Jeremy Fitzhardinge [this message]
2008-06-06  8:14     ` Jan Beulich
2008-06-06  8:15       ` Jeremy Fitzhardinge
2008-06-07 18:39         ` H. Peter Anvin
2008-06-06  4:45 ` Arjan van de Ven
2008-06-06  8:08   ` Jeremy Fitzhardinge

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=4848EE5C.6040003@goop.org \
    --to=jeremy@goop.org \
    --cc=andi@firstfloor.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable@kernel.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.