[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100120165443.GB3284@flint.arm.linux.org.uk>
Date: Wed, 20 Jan 2010 16:54:44 +0000
From: Russell King <rmk+lkml@....linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [CFT] MM: Pass a PTE pointer to update_mmu_cache() rather than
the PTE itself
On Wed, Jan 20, 2010 at 05:45:34PM +0100, Geert Uytterhoeven wrote:
> > diff --git a/Documentation/cachetlb.txt b/Documentation/cachetlb.txt
> > index da42ab4..74a8b6f 100644
> > --- a/Documentation/cachetlb.txt
> > +++ b/Documentation/cachetlb.txt
> > @@ -88,12 +88,12 @@ changes occur:
> > This is used primarily during fault processing.
> >
> > 5) void update_mmu_cache(struct vm_area_struct *vma,
> > - unsigned long address, pte_t pte)
> > + unsigned long address, pte_t *ptep)
> >
> > At the end of every page fault, this routine is invoked to
> > tell the architecture specific code that a translation
> > - described by "pte" now exists at virtual address "address"
> > - for address space "vma->vm_mm", in the software page tables.
> > + now exists at virtual address "address" for address space
> > + "vma->vm_mm", in the software page tables.
> >
> > A port may use this information in any way it so chooses.
> > For example, it could use this event to pre-load TLB
>
> Now the documentation no longer mentions what the 3rd parameter is used for?
I'm open to suggestions for a suitable description for it.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists