From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Rondonneau Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved by BIOS Date: Fri, 21 May 2010 21:58:51 -0700 Message-ID: References: <4BF42296.1030905@oracle.com> <4BF4235D.3080904@zytor.com> <4BF46D9B.4090806@zytor.com> <20100520131230.41a99489@lxorguk.ukuu.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Alan Cox Cc: "H. Peter Anvin" , Yinghai , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Ingo Molnar , Linus Torvalds List-Id: linux-arch.vger.kernel.org On Fri, May 21, 2010 at 8:15 AM, Mathieu Rondonneau wrote: > On Thu, May 20, 2010 at 5:12 AM, Alan Cox wrote: >> On Wed, 19 May 2010 17:01:41 -0700 >> Mathieu Rondonneau wrote: >> >>> it' s not in ISA space. >>> once loading the NVIDIA driver, the warnign oops shows up. >>> 4K starting at 0x9f800 (i.e. to 0xa007ff) overlap with the ISA space >>> (starting at 0xa0000). >> >> If this is the proprietary Nvidia driver you need to take the matter up >> with Nvidia. I assume they are trying to remap chunks of the EBA for some >> reason. >> >> And please can you not top post to this list, it makes it very hard to >> follow when you are replying in a different order to everyone else. >> >> Alan >> > > Thanks Alan, I will post on NVIDIA forum. Thanks for the feedback. > > Yinghai, your patch had some missing parameter for the sanitize function. > It does fixes the bios side (/proc/iomem) that now shows only aligned sections. > But it does not prevent the Nvidia driver to try to allocate on non-4K > align (i.e. if this is what' s happening). > > Thanks for the help, > -Mathieu > Found on Nvidia forum that they are aware of the problem. They said that this will be fixed in the next driver version. -Mathieu From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:51072 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751106Ab0EVE6w (ORCPT ); Sat, 22 May 2010 00:58:52 -0400 MIME-Version: 1.0 In-Reply-To: References: <4BF42296.1030905@oracle.com> <4BF4235D.3080904@zytor.com> <4BF46D9B.4090806@zytor.com> <20100520131230.41a99489@lxorguk.ukuu.org.uk> Date: Fri, 21 May 2010 21:58:51 -0700 Message-ID: Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved by BIOS From: Mathieu Rondonneau Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-arch-owner@vger.kernel.org List-ID: To: Alan Cox Cc: "H. Peter Anvin" , Yinghai , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Ingo Molnar , Linus Torvalds Message-ID: <20100522045851.vsCCZA9UrceKAbuQiyoGeiBhhW1wVoryk12bPa6F3Ao@z> On Fri, May 21, 2010 at 8:15 AM, Mathieu Rondonneau wrote: > On Thu, May 20, 2010 at 5:12 AM, Alan Cox wrote: >> On Wed, 19 May 2010 17:01:41 -0700 >> Mathieu Rondonneau wrote: >> >>> it' s not in ISA space. >>> once loading the NVIDIA driver, the warnign oops shows up. >>> 4K starting at 0x9f800 (i.e. to 0xa007ff) overlap with the ISA space >>> (starting at 0xa0000). >> >> If this is the proprietary Nvidia driver you need to take the matter up >> with Nvidia. I assume they are trying to remap chunks of the EBA for some >> reason. >> >> And please can you not top post to this list, it makes it very hard to >> follow when you are replying in a different order to everyone else. >> >> Alan >> > > Thanks Alan, I will post on NVIDIA forum. Thanks for the feedback. > > Yinghai, your patch had some missing parameter for the sanitize function. > It does fixes the bios side (/proc/iomem) that now shows only aligned sections. > But it does not prevent the Nvidia driver to try to allocate on non-4K > align (i.e. if this is what' s happening). > > Thanks for the help, > -Mathieu > Found on Nvidia forum that they are aware of the problem. They said that this will be fixed in the next driver version. -Mathieu