linux-kernel - Re: [PATCH] x86: fix /proc/meminfo DirectMap

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]

Message-ID: <20080815132854.GG30597@elte.hu>
Date:	Fri, 15 Aug 2008 15:28:54 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	Andi Kleen <andi@...stfloor.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: fix /proc/meminfo DirectMap


* Hugh Dickins <hugh@...itas.com> wrote:

> Do we actually want these DirectMap lines in the x86 /proc/meminfo? I 
> can see they're interesting to CPA developers and TLB optimizers, but 
> they don't fit its usual "where has all my memory gone?" usage. If 
> they are to stay, here are some fixes.

i think they are borderline useful - so i've applied your fixes to 
tip/x86/urgent.

> You might prefer me to split these up?

nah.

> Should we really be using level2_ident_pgt (which needs to avoid NX) 
> for the final direct map (which wants to use NX)?  But my attempt to 
> build up a fresh pagetable there failed miserably to boot!

hm, exactly what change have you tried? (patch?)

	Ingo
--
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/