From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [CFT] MM: Pass a PTE pointer to update_mmu_cache() rather than the PTE itself
Date: Wed, 20 Jan 2010 16:54:44 +0000 [thread overview]
Message-ID: <20100120165443.GB3284@flint.arm.linux.org.uk> (raw)
In-Reply-To: <10f740e81001200845o7a31bcb6yea475f3aabcb5476@mail.gmail.com>
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:
next prev parent reply other threads:[~2010-01-20 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 13:52 [CFT] MM: Pass a PTE pointer to update_mmu_cache() rather than the PTE itself Russell King
2010-01-20 16:45 ` Geert Uytterhoeven
2010-01-20 16:45 ` Geert Uytterhoeven
2010-01-20 16:54 ` Russell King [this message]
2010-01-22 3:50 ` Benjamin Herrenschmidt
2010-02-09 2:43 ` Benjamin Herrenschmidt
2010-02-09 2:43 ` Benjamin Herrenschmidt
2010-02-18 16:25 ` Russell King
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=20100120165443.GB3284@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).