From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Thomas Gleixner <tglx@linutronix.de>, "H. Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: x86 git tree broken (bisected)
Date: Mon, 14 Apr 2008 11:16:00 +0200 [thread overview]
Message-ID: <20080414091600.GI19865@elte.hu> (raw)
In-Reply-To: <86802c440804131842t16d05976g20b2eb97af6bbf1b@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.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
next prev parent reply other threads:[~2008-04-14 9:16 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 19:59 x86 git tree broken Rafael J. Wysocki
2008-04-10 20:13 ` Ingo Molnar
2008-04-10 20:25 ` Rafael J. Wysocki
2008-04-10 20:29 ` Ingo Molnar
2008-04-10 20:38 ` Ingo Molnar
2008-04-10 22:28 ` Rafael J. Wysocki
2008-04-11 19:26 ` x86 git tree broken (bisected) Rafael J. Wysocki
2008-04-11 20:23 ` Rafael J. Wysocki
2008-04-11 20:29 ` Rafael J. Wysocki
2008-04-11 20:26 ` Yinghai Lu
2008-04-11 20:51 ` Rafael J. Wysocki
2008-04-11 21:11 ` Yinghai Lu
2008-04-11 21:21 ` Rafael J. Wysocki
2008-04-11 21:31 ` Yinghai Lu
2008-04-13 8:24 ` Yinghai Lu
2008-04-13 8:41 ` Yinghai Lu
2008-04-13 16:14 ` Rafael J. Wysocki
2008-04-14 9:02 ` Ingo Molnar
2008-04-13 16:12 ` Rafael J. Wysocki
2008-04-13 18:07 ` Yinghai Lu
2008-04-13 18:47 ` Rafael J. Wysocki
2008-04-13 18:53 ` Yinghai Lu
2008-04-13 18:54 ` Yinghai Lu
2008-04-13 22:00 ` Yinghai Lu
2008-04-13 22:10 ` Rafael J. Wysocki
2008-04-13 22:32 ` Yinghai Lu
2008-04-13 23:41 ` Rafael J. Wysocki
2008-04-13 23:45 ` H. Peter Anvin
2008-04-14 0:09 ` Rafael J. Wysocki
2008-04-14 0:12 ` H. Peter Anvin
2008-04-14 0:19 ` Rafael J. Wysocki
2008-04-14 1:42 ` Yinghai Lu
2008-04-14 9:16 ` Ingo Molnar [this message]
2008-04-14 18:08 ` Yinghai Lu
2008-04-14 20:21 ` Rafael J. Wysocki
2008-04-14 21:06 ` Yinghai Lu
2008-04-14 21:09 ` Rafael J. Wysocki
2008-04-14 21:36 ` Yinghai Lu
2008-04-13 7:51 ` Ingo Molnar
2008-04-13 7:59 ` Yinghai Lu
2008-04-13 7:58 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Ingo Molnar
2008-04-13 8:18 ` Yinghai Lu
2008-04-13 9:19 ` Ingo Molnar
2008-04-13 9:39 ` [rfc] hw resource debugging checks Andi Kleen
2008-04-13 17:53 ` Arjan van de Ven
2008-04-13 18:19 ` Yinghai Lu
2008-04-13 18:29 ` Andi Kleen
2008-04-13 19:29 ` Yinghai Lu
2008-04-14 3:52 ` Arjan van de Ven
2008-04-14 5:01 ` Yinghai Lu
2008-04-14 14:12 ` Arjan van de Ven
2008-04-14 18:11 ` Yinghai Lu
2008-04-13 15:48 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Arjan van de Ven
2008-04-10 20:51 ` x86 git tree broken Ingo Molnar
2008-04-10 22:27 ` Rafael J. Wysocki
2008-04-11 6:43 ` Ingo Molnar
[not found] <fa.2mJjVaMdmV5IWp3mQiYHE1u4pHU@ifi.uio.no>
[not found] ` <fa.SO/I64FxJXD1oLBH54BTs4pc56c@ifi.uio.no>
[not found] ` <fa.fJC0A/aGr6H8XE94NUuvl1ixoc0@ifi.uio.no>
[not found] ` <fa.qs5oa+YMIJd6h2hpuGCULc8ODY4@ifi.uio.no>
2008-04-16 4:27 ` x86 git tree broken (bisected) Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080414091600.GI19865@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox