From: Eric Lacombe <tuxiko@free.fr>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: [x86_64] Implementation differences compared to x86_32
Date: Mon, 13 Oct 2008 14:26:19 +0200 [thread overview]
Message-ID: <200810131426.20075.goretux@gmail.com> (raw)
Hi,
Thanks again for all your answers.
I have some new questions with regard to x86_64 specificities.
- 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 ?
- 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.
- 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 ?
Thanks in advance
Eric
next reply other threads:[~2008-10-13 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 12:26 Eric Lacombe [this message]
2008-10-13 13:03 ` [x86_64] Implementation differences compared to x86_32 Andi Kleen
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=200810131426.20075.goretux@gmail.com \
--to=tuxiko@free.fr \
--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