From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel writes to RAM it doesn't own on 2.4.24
Date: Sat, 17 Apr 2004 20:21:54 +0000 (UTC) [thread overview]
Message-ID: <c5s3l2$6be$1@terminus.zytor.com> (raw)
In-Reply-To: 200404171440.18829.ross@datscreative.com.au
Followup to: <200404171440.18829.ross@datscreative.com.au>
By author: Ross Dickson <ross@datscreative.com.au>
In newsgroup: linux.dev.kernel
>
> 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.
>
Yup.
-hpa
next prev parent reply other threads:[~2004-04-17 20:22 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
2004-04-20 16:46 ` Ross Biro
2004-04-17 20:21 ` H. Peter Anvin [this message]
-- 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='c5s3l2$6be$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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