From: Frank Mehnert <Frank.Mehnert@Sun.COM>
To: linux-kernel@vger.kernel.org
Subject: remap_pfn_range() not suitable for physical RAM?
Date: Wed, 04 Mar 2009 20:25:46 +0100 [thread overview]
Message-ID: <200903042025.46861.frank.mehnert@sun.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 404 bytes --]
Hi,
since 2.6.29-rcX it seems to be not allowed anymore to use
remap_pfn_range() to remap physical RAM to userland. This restriction
applies only if CONFIG_X86_PAT is enabled. It seems that vm_insert_page()
does not have this restriction. Am I correct? And what is the reason
for this restriction?
Kind regards,
Frank
--
Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-04 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 19:25 Frank Mehnert [this message]
2009-03-10 8:04 ` remap_pfn_range() not suitable for physical RAM? Frank Mehnert
2009-03-10 17:33 ` Pallipadi, Venkatesh
2009-03-13 15:00 ` Frank Mehnert
2009-03-13 17:13 ` Pallipadi, Venkatesh
2009-03-14 11:44 ` Frank Mehnert
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=200903042025.46861.frank.mehnert@sun.com \
--to=frank.mehnert@sun.com \
--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