linux-kernel - Re: x86 git tree broken (bisected)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080414091600.GI19865@elte.hu>
Date:	Mon, 14 Apr 2008 11:16:00 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Anvin" <hpa@...or.com>, Arjan van de Ven <arjan@...radead.org>
Subject: Re: x86 git tree broken (bisected)

* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> >  Attached is dmesg output from current x86.git with 
> >  debug_gart_checking.patch applied.
> 
> please test the final one ... ...
> 
> You should get back 64M memory back.

so basically with all the right patches applied, and GART set to 32MB in 
the BIOS, Rafael should have more free RAM on his system than ever 
before :-)

i've put all the patches into x86.git/latest (it's all uploaded already 
as well), so that should give Rafael a one-stop shop to test it out. [i 
have not applied the debug patch that changes the aperture test from 
32MB to 64MB, and it should be unnecessary as well]

btw., Yinghai, should we perhaps add a WARN_ON() to those places where 
we waste RAM (such as the "This costs you 64 MB of RAM" message) - so 
that kerneloops.org can pick those warnings up? Maybe there are other 
situations where we waste RAM, and people dont realize it.

	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/