From: Ross Biro <ross.biro@gmail.com>
To: ross@datscreative.com.au
Cc: linux-kernel@vger.kernel.org, root@chaos.analogic.com
Subject: Re: Kernel writes to RAM it doesn't own on 2.4.24
Date: Sat, 17 Apr 2004 08:40:31 -0400 [thread overview]
Message-ID: <7FF8CDFE.64C50807@mail.gmail.com> (raw)
In-Reply-To: 200404171440.18829.ross@datscreative.com.au
On Sat, 17 Apr 2004 14:40:18 +1000, Ross Dickson
<ross@datscreative.com.au> wrote:
> This is all most enlightening. If I am understanding correctly then every
> device driver that the author specifies to use a "mem=" command to
> reserve some memory for said drivers use at the upper part of physical
> memory is stuffed by design.
The problem is really that Linux doesn't trust the BARs assigned by
the PCI bios because some BIOSes do it incorrectly. So it reprograms
them based on the memory map it got from the BIOS. However, before it
does that the mem= parameter overrides the memory map from the BIOS.
I believe what I did was to save a copy of the e820 maps for later,
and then take then take the first free address as the max of the first
free address from the user supplied map and the bios supplied map.
I'll send out a patch on Tuesday.
Ross
next prev parent reply other threads:[~2004-04-17 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 4:40 Kernel writes to RAM it doesn't own on 2.4.24 Ross Dickson
2004-04-17 12:40 ` Ross Biro [this message]
2004-04-20 16:46 ` Ross Biro
2004-04-17 20:21 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 15:55 Richard B. Johnson
2004-04-16 16:09 ` Ross Biro
2004-04-16 16:55 ` Richard B. Johnson
2004-04-16 17:07 ` Ross Biro
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=7FF8CDFE.64C50807@mail.gmail.com \
--to=ross.biro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=ross@datscreative.com.au \
/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