mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Frank Mehnert <Frank.Mehnert@Sun.COM>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: remap_pfn_range() not suitable for physical RAM?
Date: Fri, 13 Mar 2009 10:13:36 -0700	[thread overview]
Message-ID: <1236964416.4529.125.camel@localhost.localdomain> (raw)
In-Reply-To: <200903131600.00463.frank.mehnert@sun.com>


Frank,

The track and untrack is keeping track of memory type for non-RAM
regions and making sure that the type is in sync for various mappings
for such addresses. We are not tracking the RAM pages today, so
vm_insert_page does not have this. vm_insert_mixed is also not covered
today, as we deferred that and tracking of RAM pages into our next set
of changes.

Thanks,
Venki

On Fri, 2009-03-13 at 08:00 -0700, Frank Mehnert wrote:
> Venki,
> 
> thanks for your reply. May I ask anyway why this check is done in 
> remap_pfn_range() and vm_insert_pfn() but not in vm_insert_page()?
> 
> Kind regards,
> 
> Frank
> 
> On Tuesday 10 March 2009, Pallipadi, Venkatesh wrote:
> > 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/
> > >--
> >
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> 
> 


  reply	other threads:[~2009-03-13 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 19:25 Frank Mehnert
2009-03-10  8:04 ` Frank Mehnert
2009-03-10 17:33   ` Pallipadi, Venkatesh
2009-03-13 15:00     ` Frank Mehnert
2009-03-13 17:13       ` Pallipadi, Venkatesh [this message]
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=1236964416.4529.125.camel@localhost.localdomain \
    --to=venkatesh.pallipadi@intel.com \
    --cc=Frank.Mehnert@Sun.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=suresh.b.siddha@intel.com \
    /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

all inboxes | Powered by JetHome®