linux-kernel - Re: [Provisional Page Table] Why the linear address ranges starting both from 0 and PAGE_OFFSET are mapped to the same physical address range in the provisional page table?

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-prev] [day] [month] [year] [list]

Message-ID: <CAMzpN2heyNKNryBgHJv__Nbkr9QQJuCBrpSDj=tSd-yuHqaowA@mail.gmail.com>
Date:	Sat, 3 Dec 2011 01:54:34 -0500
From:	Brian Gerst <brgerst@...il.com>
To:	zhihua che <zhihua.che@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Provisional Page Table] Why the linear address ranges starting
 both from 0 and PAGE_OFFSET are mapped to the same physical address range in
 the provisional page table?

On Sat, Dec 3, 2011 at 12:27 AM, zhihua che <zhihua.che@...il.com> wrote:
> Here is another relating question. Why the provisional page table is
> stored at initial_page_table while final page table is store at
> swapper_pg_dir, I think only one page directory table is enough,
> because the two page table are not effective in the same time, it's
> enough to construct the provisional page table at swapper_pg_dir, then
> clear it and construct the final page table. And I find that in the
> previous linux kernel, only swapper_pg_dir is present.

See commits fd89a137924e0710078c3ae855e7cec1c43cb845 and
b40827fa7268fda8a62490728a61c2856f33830b for the explanation of why
they are seperate.

--
Brian Gerst
--
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/