From: Timur Tabi <ttabi@interactivesi.com>
To: Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: Allocating a page of memory with a given physical address
Date: Thu, 08 Jun 2000 17:27:42 -0500 [thread overview]
Message-ID: <20000608225108Z131165-245+107@kanga.kvack.org> (raw)
In-Reply-To: <yttd7lrq0ok.fsf@serpe.mitica>
** Reply to message from "Juan J. Quintela" <quintela@fi.udc.es> on 09 Jun 2000
00:15:39 +0200
> 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.
Unfortunately, that's not an option. We need to be able to reserve/allocate
pages in a driver's init_module() function, and I don't mean drivers that are
compiled with the kernel. We need to be able to ship a stand-alone driver that
can work with pretty much any Linux distro of a particular version (e.g. we can
say that only 2.4.14 and above is supported).
For the time being, we can work with a patch to the kernel, but that patch be
relatively generic, and it must support our dynamically loadable driver.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
--
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:27 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
2000-06-08 22:27 ` Timur Tabi [this message]
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=20000608225108Z131165-245+107@kanga.kvack.org \
--to=ttabi@interactivesi.com \
--cc=linux-mm@kvack.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