linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Memory Management <linux-mm@kvack.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 3/3] mm: fault handler to replace nopage and populate
Date: Mon, 09 Oct 2006 21:32:59 +1000	[thread overview]
Message-ID: <1160393579.10229.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20061009111906.GA26824@wotan.suse.de>

On Mon, 2006-10-09 at 13:19 +0200, Nick Piggin wrote:
> On Mon, Oct 09, 2006 at 09:10:13PM +1000, Benjamin Herrenschmidt wrote:
> > 
> > > Yep, I see. You just need to be careful about the PFNMAP logic, so
> > > the VM knows whether the pte is backed by a struct page or not.
> > 
> > I still need to properly get my head around that one. I can't easily
> > change the VMA during the "switch" but I can tweak the flags on the
> > first nopage after one... 
> 
> You'll want to clear VM_PFNMAP after unmapping all pages from it, before
> switching to struct page backing.

Which means having a list of all vma's ... I suppose I can look at the
truncate code to do that race free but I was hoping I could avoid it
(that's the whole point of using unmap_mapping_range() in fact).
 
> > > And going the pageless route means that you must disallow MAP_PRIVATE
> > > PROT_WRITE mappings, I trust that isn't a problem for you?
> > 
> > Should not but I need to look more closely.
> 
> If you do need to, then if your pfns are contiguous in virtual memory,
> and you can spare vm_pgoff, then you can use remap_pfn_range's method
> of setting vm_pgoff to the first pfn.

Yup. I got that bit.

> I can add a bit of sanity checking for that as well.
> 
> > > +	/* Ok, finally just insert the thing.. */
> > > +	set_pte_at(mm, addr, pte, pfn_pte(pfn, vma->vm_page_prot));
> > > +
> > > +	vma->vm_flags |= VM_PFNMAP;
> > > +	retval = 0;
> > > +out_unlock:
> > > +	pte_unmap_unlock(pte, ptl);
> > > +out:
> > > +	return retval;
> > > +}
> > > +EXPORT_SYMBOL(vm_insert_pfn);
> > 
> > It also needs update_mmu_cache() I suppose.
> 
> Hmm, but it might not be called from a pagefault. Can we get away
> with not calling it? Or is it required by some architectures?

I think some architectures might be upset if it's not called...

Ben.


--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-10-09 11:32 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 13:05 [rfc] 2.6.19-rc1: vm stuff Nick Piggin
2006-10-07 13:05 ` [patch 1/3] mm: arch_free_page fix Nick Piggin
2006-10-07 13:05 ` [patch 2/3] mm: locks_freed fix Nick Piggin
2006-10-07 13:06 ` [patch 3/3] mm: add arch_alloc_page Nick Piggin
2006-10-07 20:43   ` Andrew Morton
2006-10-08  1:39     ` Nick Piggin
2006-10-11 14:48       ` Martin Schwidefsky
2006-10-11 14:56         ` Nick Piggin
2006-10-11 15:07           ` Martin Schwidefsky
2006-10-07 13:06 ` [patch 1/3] mm: fault vs invalidate/truncate check Nick Piggin
2006-10-07 13:06 ` [patch 2/3] mm: fault vs invalidate/truncate race fix Nick Piggin
2006-10-07 20:43   ` Andrew Morton
2006-10-07 20:44   ` Andrew Morton
2006-10-08  2:05     ` Nick Piggin
2006-10-07 13:06 ` [patch 3/3] mm: fault handler to replace nopage and populate Nick Piggin
2006-10-07 15:14   ` Jeff Garzik
2006-10-08  2:17     ` Nick Piggin
2006-10-07 20:44   ` Andrew Morton
2006-10-08  2:12     ` Nick Piggin
2006-10-08 23:46     ` Benjamin Herrenschmidt
2006-10-09 10:26       ` Nick Piggin
2006-10-09 10:50         ` Benjamin Herrenschmidt
2006-10-09 11:00           ` Nick Piggin
2006-10-09 11:10             ` Benjamin Herrenschmidt
2006-10-09 11:19               ` Nick Piggin
2006-10-09 11:32                 ` Benjamin Herrenschmidt [this message]
2006-10-09 11:45                   ` Nick Piggin
2006-10-09 11:49                     ` Benjamin Herrenschmidt
2006-10-09 11:58                       ` Nick Piggin
2006-10-09 12:07                         ` Benjamin Herrenschmidt
2006-10-09 12:14                           ` Nick Piggin
2006-10-09 13:38                             ` Thomas Hellstrom
2006-10-09 13:52                               ` Nick Piggin
2006-10-09 20:50                                 ` Benjamin Herrenschmidt
2006-10-10  6:11                                   ` Thomas Hellström
2006-10-10  7:55                                     ` Benjamin Herrenschmidt
2006-10-10  8:39                                       ` Thomas Hellstrom
2006-10-09 20:45                               ` Benjamin Herrenschmidt
2006-10-09 12:09                         ` Nick Piggin
2006-10-09 12:11                           ` Benjamin Herrenschmidt
2006-10-10 12:10   ` Christoph Hellwig
2006-10-10 12:13     ` Nick Piggin
2006-10-10 17:52       ` Andrew Morton
2006-10-11  0:43         ` SPAM: " Nick Piggin
     [not found]   ` <5c77e7070610120456t1bdaa95cre611080c9c953582@mail.gmail.com>
2006-10-12 12:07     ` Nick Piggin
2006-10-14 13:28       ` Ingo Oeser
2006-10-15  7:54         ` Nick Piggin
2006-10-24 21:31   ` Dave Airlie
2006-10-26 11:09     ` Nick Piggin

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=1160393579.10229.24.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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