linux-kernel - [x86_64] Implementation differences compared to x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200810131426.20075.goretux@gmail.com>
Date:	Mon, 13 Oct 2008 14:26:19 +0200
From:	Eric Lacombe <tuxiko@...e.fr>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [x86_64] Implementation differences compared to x86_32

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/