From: "H. Peter Anvin" <hpa@zytor.com>
To: Mathieu Rondonneau <mathieu.rondonneau@gmail.com>
Cc: 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: Wed, 19 May 2010 17:09:19 -0700 [thread overview]
Message-ID: <4BF47DAF.5040409@zytor.com> (raw)
In-Reply-To: <AANLkTiltANJ9eaGBkfJJOyZ8skCxxOmkAs1UvCLB_YQ9@mail.gmail.com>
On 05/19/2010 05:01 PM, 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).
>
> When I don' t load the driver, no oops.
> So I am assuming nvidia driver request 4K of memory, that happens to
> be available in the bios area.
>
> I think that there is a check missing somewhere to report that
> available RAM buffer is already reserved (by BIOS) so we need to get
> it from somewhere else.
>
> Does it make sense?
> -Mathieu
No.
The top page (0x9f000) is generally also reserved... there is pretty
much always BIOS data structures there.
It sounds like the Nvidia driver is trying to map those, and doing it
incorrectly. -ENVIDIA.
-hpa
next prev parent reply other threads:[~2010-05-20 0:10 UTC|newest]
Thread overview: 13+ 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 [this message]
2010-05-20 12:12 ` Alan Cox
2010-05-20 12:12 ` Alan Cox
2010-05-21 15:15 ` Mathieu Rondonneau
2010-05-22 4:58 ` Mathieu Rondonneau
2010-05-22 4:58 ` Mathieu Rondonneau
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=4BF47DAF.5040409@zytor.com \
--to=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.rondonneau@gmail.com \
--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).