Messages in this thread | | | From | "Pallipadi, Venkatesh" <> | Date | Tue, 10 Mar 2009 10:33:31 -0700 | Subject | RE: remap_pfn_range() not suitable for physical RAM? |
| |
Frank,
Patch here should eliminate the restriction. http://marc.info/?l=linux-kernel&m=123664923030126&w=1
Thanks, Venki
>-----Original Message----- >From: linux-kernel-owner@vger.kernel.org >[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Frank Mehnert >Sent: Tuesday, March 10, 2009 1:04 AM >To: linux-kernel@vger.kernel.org >Cc: peterz@infradead.org; Siddha, Suresh B >Subject: Re: remap_pfn_range() not suitable for physical RAM? > >Hi, > >sorry for re-posting this message and sorry for addressing you >directly. >Perhaps you can help me again or can you give me a pointer for a proper >documentation of the various *remap* and *vm_insert* functions: > >On Wednesday 04 March 2009, Frank Mehnert wrote: >> 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/ >
| |