From: cohutta <cohutta@MailAndNews.com>
To: linux-mm@kvack.org
Subject: Re: temp. mem mappings
Date: Tue, 5 Jun 2001 16:42:52 -0400 [thread overview]
Message-ID: <3B581215@MailAndNews.com> (raw)
> > > Allocate a virtual memory area using vmalloc and then save and
modify the
> > > pmd/pgd/pte to point to the physical memory you want. To unmap,
just undo the
> > > previous steps.
> >
> > ioremap() is there for exactly that purpose.
>
> True, except that you can't use ioremap on normal memory, which is
what I
> assumed he was trying to do.
Normal memory is identity-mapped very early in boot anyway (except for
highmem on large Intel boxes, that is, and kmap() works for that.)
---
I don't really want to play with the page tables if i can help it.
I didn't use ioremap() because it's real system memory, not IO bus
memory.
How much normal memory is identity-mapped at boot on x86?
Is it more than 8 MB?
I'm trying to read some ACPI tables, like the FACP.
On my system, this is at physical address 0x3fffd7d7 (e.g.).
kmap() ends up calling set_pte(), which is close to what i am
already doing. i'm having a problem on the unmap side when i
am done with the temporary mapping.
thanks.
/cohutta/
--
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-mm.org/
next reply other threads:[~2001-06-05 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 20:42 cohutta [this message]
2001-06-05 20:59 ` Timur Tabi
2001-06-05 22:27 ` Joseph A. Knapka
2001-06-06 8:23 ` Stephen C. Tweedie
-- strict thread matches above, loose matches on Subject: below --
2001-06-11 16:32 cohutta
2001-06-25 6:52 ` Eric W. Biederman
2001-06-08 1:38 cohutta
2001-06-08 17:02 ` Joseph A. Knapka
2001-06-08 18:07 ` Stephen C. Tweedie
2001-06-08 21:22 ` Joseph A. Knapka
2001-06-06 21:14 cohutta
2001-06-07 10:00 ` Stephen C. Tweedie
2001-06-05 17:54 cohutta
2001-06-05 18:25 ` Timur Tabi
2001-06-05 18:41 ` Stephen C. Tweedie
2001-06-05 18:51 ` Timur Tabi
2001-06-05 18:59 ` Stephen C. Tweedie
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=3B581215@MailAndNews.com \
--to=cohutta@mailandnews.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