linux-kernel - Re: [PATCH v7u1 09/31] x86, 64bit: #PF handler set page to cover 2M only

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

Date:	Wed, 9 Jan 2013 23:57:36 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jan Kiszka <jan.kiszka@....de>,
	Jason Wessel <jason.wessel@...driver.com>,
	linux-kernel@...r.kernel.org,
	Alexander Duyck <alexander.h.duyck@...el.com>
Subject: Re: [PATCH v7u1 09/31] x86, 64bit: #PF handler set page to cover 2M
 only

On Thu, Jan 03, 2013 at 04:48:29PM -0800, Yinghai Lu wrote:
> Now #PF hanlder could map 1G per #PF, That causes same problem that
> is fixed by
> 	x86, mm: Only direct map addresses that are marked as E820_RAM
> 
> only add one 2M mapping instead of 1G accessing one time for dynamically
> per #PF.

Ok, I can more or less grasp what the code does but this sentence above
is a lot of fun. Do you mean:

"add only one 2M mapping per #PF instead of all 512 pmds comprising 1G"

?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/