[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinEXX6ZQoauZH3Du-z69Lx_xoUfzTb8vxhoc09i@mail.gmail.com>
Date: Fri, 21 May 2010 08:15:08 -0700
From: Mathieu Rondonneau <mathieu.rondonneau@...il.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@...or.com>, Yinghai <yinghai.lu@...cle.com>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved by
BIOS
On Thu, May 20, 2010 at 5:12 AM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Wed, 19 May 2010 17:01:41 -0700
> Mathieu Rondonneau <mathieu.rondonneau@...il.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists