From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763064AbXHHQBA (ORCPT ); Wed, 8 Aug 2007 12:01:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760108AbXHHQAn (ORCPT ); Wed, 8 Aug 2007 12:00:43 -0400 Received: from one.firstfloor.org ([213.235.205.2]:59347 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758540AbXHHQAm (ORCPT ); Wed, 8 Aug 2007 12:00:42 -0400 Date: Wed, 8 Aug 2007 18:00:39 +0200 From: Andi Kleen To: =?iso-8859-1?Q?C=E9dric?= Augonnet Cc: Andi Kleen , Loic Prylli , Linux Kernel Mailing List , Andrew Morton , brice@myri.com, cedric.augonnet@ens-lyon.org Subject: Re: PAT support for i386 and x86_64 Message-ID: <20070808160039.GA16357@one.firstfloor.org> References: <20070807083004.GB30085@one.firstfloor.org> <46B97E39.3020905@myri.com> <20070808101441.GA12861@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 08, 2007 at 11:42:17AM -0400, Cédric Augonnet wrote: > changing this register is absolutely not the actual issue with PAT, but > don't > you think such a first step is needed to avoid conflicts since people _do_ > already set that register from their driver. Which drivers do that? Ok, I know the ATI 3d driver does, but if that crashes the users know who is to blame. No, I don't think we should merge a potentially data corrupting "first step.". Even first steps have to meet some standards. > Of course there is no problem for that being dependant on a CONFIG_PAT. I don't think a CONFIG_DATA_CORRUPTION is a good idea. -Andi