Message-ID: <479A3222.30008@goop.org>
Date: Fri, 25 Jan 2008 11:01:54 -0800
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Thunderbird 2.0.0.9 (X11/20071115)
MIME-Version: 1.0
To: Ingo Molnar <mingo@elte.hu>
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
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> <20080125185923.GA2518@elte.hu>
In-Reply-To: <20080125185923.GA2518@elte.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1067
Lines: 34

Ingo Molnar wrote:
> * 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! :-)
>   

I was referring to:

commit 6a4544a9c8b54b82893044cb53695502cc386f00
Author: Yinghai Lu <Yinghai.Lu@Sun.COM>
Date:   Fri Jan 25 00:15:29 2008 +0100

    x86_32: trim memory by updating e820 v3


but you've answered the question...

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