From: Eric Lacombe <goretux@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, linux-kernel@vger.kernel.org
Subject: Re: [x86_64] Implementation differences compared to x86_32
Date: Mon, 13 Oct 2008 15:28:17 +0200 [thread overview]
Message-ID: <200810131528.17115.goretux@gmail.com> (raw)
In-Reply-To: <87vdvwr6k9.fsf@basil.nowhere.org>
On Monday 13 October 2008 15:03:02 Andi Kleen wrote:
> Eric Lacombe <tuxiko@free.fr> writes:
> > - In x86_32, the physical memory is mapped on kernel land by way of 4 MB
> > pages.
> > But for x86_64, I read that the physical memory was mapped by way of 4 KB
> > pages. Is it true ? and in this case, why this choice ?
>
> It's normally not true (except in some special circumstances)
What are these particular circumstances ?
Eric
prev parent reply other threads:[~2008-10-13 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 12:26 [x86_64] Implementation differences compared to x86_32 Eric Lacombe
2008-10-13 13:03 ` Andi Kleen
2008-10-13 13:28 ` Eric Lacombe [this message]
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=200810131528.17115.goretux@gmail.com \
--to=goretux@gmail.com \
--cc=andi@firstfloor.org \
--cc=jeremy@goop.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