From: Mathieu Rondonneau <mathieu.rondonneau@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Yinghai <yinghai.lu@oracle.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Prevent reserving RAM in the region already reserved by BIOS
Date: Fri, 21 May 2010 21:58:51 -0700 [thread overview]
Message-ID: <AANLkTin8oSAGka-bkSuWFvW0b_VyEDdGmwGmJXiw3Oyp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinEXX6ZQoauZH3Du-z69Lx_xoUfzTb8vxhoc09i@mail.gmail.com>
On Fri, May 21, 2010 at 8:15 AM, Mathieu Rondonneau
<mathieu.rondonneau@gmail.com> wrote:
> On Thu, May 20, 2010 at 5:12 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> On Wed, 19 May 2010 17:01:41 -0700
>> Mathieu Rondonneau <mathieu.rondonneau@gmail.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
>
Found on Nvidia forum that they are aware of the problem. They said
that this will be fixed in the next driver version.
-Mathieu
prev parent reply other threads:[~2010-05-22 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 5:35 [PATCH] Prevent reserving RAM in the region already reserved by BIOS Mathieu Rondonneau
2010-05-19 17:40 ` Yinghai
2010-05-19 17:43 ` H. Peter Anvin
2010-05-19 22:58 ` Mathieu Rondonneau
2010-05-19 23:00 ` H. Peter Anvin
2010-05-20 0:01 ` Mathieu Rondonneau
2010-05-20 0:07 ` Yinghai
2010-05-20 0:09 ` H. Peter Anvin
2010-05-20 12:12 ` Alan Cox
2010-05-21 15:15 ` Mathieu Rondonneau
2010-05-22 4:58 ` Mathieu Rondonneau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTin8oSAGka-bkSuWFvW0b_VyEDdGmwGmJXiw3Oyp@mail.gmail.com \
--to=mathieu.rondonneau@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yinghai.lu@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).