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 18:29:07 -0500 [thread overview]
Message-ID: <20000608235235Z131165-283+94@kanga.kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0006082003120.22665-100000@duckman.distro.conectiva>
** Reply to message from Rik van Riel <riel@conectiva.com.br> on Thu, 8 Jun
2000 20:09:57 -0300 (BRST)
> Linus his policy on this is pretty strict. We won't kludge
> stuff into our kernel just to support some proprietary driver.
Well, the idea is to make it some kind of elegant enhancement that Linus would
approve of.
My idea is to create a new API, call it alloc_phys() or get_phys_page() or
whatever, that will scan the ???? (whatever the virtual memory manager calls
those things that keep track of unused virtual memory) until it finds a block
that points to the given physical address. It then allocates that particular
block.
Of course, from what little I know of the Linux VM, it looks like I'm in for a
rocky trip. For one thing, I don't understand how kernel virtual memory can
have a one-to-one mapping with physical memory, but user virtual memory has to
go through three levels of page tables. When I call get_free_page, it updates
some entry in mem_map. What is the mechanism that updates the page tables? I
figure the page tables need to be updated, so that a user process can't allocate
the same physical memory.
--
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 23:29 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
2000-06-08 23:03 ` Stephen C. Tweedie
2000-06-08 23:09 ` Rik van Riel
2000-06-08 23:29 ` Timur Tabi [this message]
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=20000608235235Z131165-283+94@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