From: James Stevenson <james@stev.org>
To: Duncan Sands <baldrick@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving physical memory at boot time
Date: 03 Dec 2002 23:23:21 +0000 [thread overview]
Message-ID: <1038957801.13490.5.camel@god.stev.org> (raw)
In-Reply-To: <200212031303.16487.baldrick@wanadoo.fr>
On Tue, 2002-12-03 at 12:03, Duncan Sands wrote:
> I would like to reserve a particular page of physical memory when
> the kernel boots. By reserving I mean that no one else gets to read
> from it or write to it: it is mine. Any suggestions for the best way
> to go about this with a 2.5 kernel?
try having a look for the linux badmem patches i belive they might do
the same sort of thing.
James
next prev parent reply other threads:[~2002-12-04 2:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 12:03 Reserving physical memory at boot time Duncan Sands
2002-12-03 21:11 ` Richard B. Johnson
2002-12-03 12:52 ` Duncan Sands
2002-12-03 22:14 ` Alan Cox
2002-12-03 21:58 ` Alan Cox
2002-12-03 22:18 ` bzeeb-lists
2002-12-04 13:25 ` Richard B. Johnson
[not found] ` <Pine.LNX.3.95.1021204082313.23777A-100000@chaos.analogic.c om>
2002-12-04 16:44 ` Mike Galbraith
2002-12-04 6:15 ` Duncan Sands
2002-12-05 5:44 ` Mike Galbraith
2002-12-04 17:01 ` Richard B. Johnson
2002-12-04 17:06 ` Randy.Dunlap
2003-03-05 5:44 ` H. Peter Anvin
2003-03-05 6:01 ` Randy.Dunlap
2003-03-05 15:04 ` H. Peter Anvin
2003-03-05 15:43 ` Randy.Dunlap
2003-03-05 15:48 ` H. Peter Anvin
2003-03-06 21:26 ` Pavel Machek
2003-03-06 23:24 ` H. Peter Anvin
2003-03-07 23:19 ` Pavel Machek
2003-03-09 21:08 ` H. Peter Anvin
2003-03-09 23:07 ` Randy.Dunlap
2002-12-03 23:23 ` James Stevenson [this message]
2002-12-04 3:53 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 8:13 Suparna Bhattacharya
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=1038957801.13490.5.camel@god.stev.org \
--to=james@stev.org \
--cc=baldrick@wanadoo.fr \
--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