Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758948AbXF0LoS (ORCPT ); Wed, 27 Jun 2007 07:44:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752135AbXF0LoK (ORCPT ); Wed, 27 Jun 2007 07:44:10 -0400 Received: from lucidpixels.com ([75.144.35.66]:55514 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751029AbXF0LoK (ORCPT ); Wed, 27 Jun 2007 07:44:10 -0400 Date: Wed, 27 Jun 2007 07:44:08 -0400 (EDT) From: Justin Piszcz X-X-Sender: jpiszcz@p34.internal.lan To: Pim Zandbergen cc: Andi Kleen , Jesse Barnes , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, "Eric W. Biederman" , Yinghai Lu Subject: Re: [PATCH] trim memory not covered by WB MTRRs In-Reply-To: <46824CA5.2020908@macroscoop.nl> Message-ID: References: <200706251434.43863.jesse.barnes@intel.com> <46823F71.6060200@macroscoop.nl> <20070627112216.GA31708@one.firstfloor.org> <46824CA5.2020908@macroscoop.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 803 Lines: 31 On Wed, 27 Jun 2007, Pim Zandbergen wrote: > Andi Kleen wrote: > >> That's impossible. Either it limited your RAM or it didn't change anything. > > OK, maybe it's cosmetic, but I would not expect a negative number > > With old BIOS it printed > **** MTRRs don't cover all of memory, trimmed 196608 pages > > with new BIOS it prints > **** MTRRs don't cover all of memory, trimmed -65536 pages > > Pim > It works ok for me: [ 0.000000] **** MTRRs don't cover all of memory, trimmed 16384 pages This is using his latest patch with 2.6.22-rc6. Justin. - 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/