From: Andi Kleen <andi@firstfloor.org>
To: Eric Lacombe <tuxiko@free.fr>
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:03:02 +0200 [thread overview]
Message-ID: <87vdvwr6k9.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200810131426.20075.goretux@gmail.com> (Eric Lacombe's message of "Mon, 13 Oct 2008 14:26:19 +0200")
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)
>
> - Is the LDT used in x86_64 ?
> I saw that the GDT_ENTRY_LDT is defined to 10 but when I read in the GDT at
> 0x50 for the segment descriptor, there is nothing, the area is filled with
> zeros.
The LDT is only allocated when the user space program needs it. That's
normally only older 32bit applications. Newer 32bit kernels also
use the same setup. Older 32bit kernels still had an iBCS entry
point in a default LDT, but that has been considered obsolete
for some time and removed.
>
> - Where can I find some documentation about the specifities of x86_64 compared
> to x86_32, particularly about memory management ?
> Perhaps you can (or someone on the list) depict those specificities ?
An somewhat outdated but still reasonable introduction is my old
paper http://halobates.de/x86-64.pdf
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-10-13 13:03 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 [this message]
2008-10-13 13:28 ` Eric Lacombe
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=87vdvwr6k9.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tuxiko@free.fr \
/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