Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755369AbXITMK0 (ORCPT ); Thu, 20 Sep 2007 08:10:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752473AbXITMKR (ORCPT ); Thu, 20 Sep 2007 08:10:17 -0400 Received: from one.firstfloor.org ([213.235.205.2]:58855 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752245AbXITMKQ (ORCPT ); Thu, 20 Sep 2007 08:10:16 -0400 Date: Thu, 20 Sep 2007 14:10:13 +0200 From: Andi Kleen To: Avi Kivity Cc: Andi Kleen , Jesse Barnes , Howard Chu , linux-kernel Subject: Re: MTRR initialization Message-ID: <20070920121013.GH18707@one.firstfloor.org> References: <46EAB7DA.10507@symas.com> <200709191452.57505.jesse.barnes@intel.com> <46F26208.309@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F26208.309@qumranet.com> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 429 Lines: 11 > Is there any reason not to set the MTRRs to define the entire memory as > write back, and use PAT exclusively for setting cacheability? That risks breaking SMM or BIOS code. -Andi - 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/