Date: Fri, 25 Jan 2008 19:59:23 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <Yinghai.Lu@Sun.COM>, "H. Peter Anvin" <hpa@zytor.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: trim ram need to check if mtrr is there v3
Message-ID: <20080125185923.GA2518@elte.hu>
References: <47993F1A.5070408@goop.org> <200801241947.55223.yinghai.lu@sun.com> <4799930B.40006@goop.org> <200801250042.53074.yinghai.lu@sun.com> <20080125110935.GA20026@elte.hu> <479A30A3.7050305@goop.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <479A30A3.7050305@goop.org>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 776
Lines: 20


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

>> thanks, applied. Shouldnt we put in an exception for when there is 
>> MTRR support, but they dont cover anything. Still emit a warning - 
>> but booting up real slow is still better than losing all of RAM and 
>> crashing
>
> The problem is re-occuring for me with current x86.git.  Looks like v2 
> did the trick, and v3 is broken...

which git head is that? I'm pushing out the queue with v3 included this 
very minute, so i doubt you can have tested that already! :-)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/