From: "Juan J. Quintela" <quintela@fi.udc.es>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: Allocating a page of memory with a given physical address
Date: 09 Jun 2000 00:15:39 +0200 [thread overview]
Message-ID: <yttd7lrq0ok.fsf@serpe.mitica> (raw)
In-Reply-To: Timur Tabi's message of "Thu, 08 Jun 2000 16:58:13 -0500"
>>>>> "timur" == Timur Tabi <ttabi@interactivesi.com> writes:
timur> ** Reply to message from "Stephen C. Tweedie" <sct@redhat.com> on Thu, 8 Jun
timur> 2000 22:47:44 +0100
>> No, nor is it likely to be added without a compelling reason. Why do
>> you need this?
timur> Unfortunately, it's part of my company's upcoming product, and I can't give a
timur> detailed explanation. I understand that such a response does not endear me to
timur> the Linux community, but my hands are tied. All I can say is that all of us
timur> software guys here have given it a lot of thought, and we're absolutely positive
timur> that we need this functionality. We need to be able to read/write memory to
timur> specific DIMMs.
Try to grep the kernel for mem_map_reserve uses, it does something
similar, and can be similar to what you want to do. Notice that you
need to reserve the page *soon* in the boot process.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-08 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 21:44 Timur Tabi
2000-06-08 21:47 ` Stephen C. Tweedie
2000-06-08 21:58 ` Timur Tabi
2000-06-08 22:15 ` Juan J. Quintela [this message]
2000-06-08 22:27 ` Timur Tabi
2000-06-08 23:03 ` Stephen C. Tweedie
2000-06-08 23:09 ` Rik van Riel
2000-06-08 23:29 ` Timur Tabi
2000-06-09 21:20 ` Jamie Lokier
2000-06-09 23:04 ` Timur Tabi
2000-06-09 21:34 ` Rik van Riel
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=yttd7lrq0ok.fsf@serpe.mitica \
--to=quintela@fi.udc.es \
--cc=linux-mm@kvack.org \
--cc=ttabi@interactivesi.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