From: Andrew Morton <akpm@linux-foundation.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-arch@vger.kernel.org, davem@davemloft.net,
hugh@veritas.com
Subject: Re: + sparc64-rename-tlb_flush_mmu.patch added to -mm tree
Date: Tue, 17 Jul 2007 14:42:45 -0700 [thread overview]
Message-ID: <20070717144245.7760a716.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070717211445.GC16147@flint.arm.linux.org.uk>
On Tue, 17 Jul 2007 22:14:45 +0100
Russell King <rmk@arm.linux.org.uk> wrote:
> On Tue, Jul 17, 2007 at 12:08:20PM -0700, Andrew Morton wrote:
> > On Tue, 17 Jul 2007 19:18:43 +0100 Russell King <rmk@arm.linux.org.uk> wrote:
> >
> > > On Tue, Jul 17, 2007 at 03:56:23PM +0200, Martin Schwidefsky wrote:
> > > > On Tue, 2007-07-17 at 01:03 -0700, Andrew Morton wrote:
> > > > > OK, I don't understand how this patch works - from a quick glance it
> > > > > appears to be forgetting to flush stuff altogether on arm and arm26 at
> > > > > least and I see no sign that Russell, Tony and Ian have even seen it.
> > > >
> > > > Added linux-arch so that affected arch-maintainers can comment.
> > >
> > > Having a little more information about Andrew's concern would be nice.
> > > Under what circumstances do you think we're forgetting to flush stuff?
> > >
> >
> > "quick glance". ARM's tlb_flush_mmu() becomes a no-op and I though that
> > some real tlb_finish_mmu() got replaced by that. But I didn't look very
> > closely.
>
> I don't think ARM will have a problem with this change.
>
> In the fullmm case, tlb_finish_mmu() will flush the entire mm, so
> missing out the flush for each chunk is itself a worthwhile optimisation.
>
> In the !fullmm case, tlb_finish_mmu() does nothing as far as flushing
> is concerned, and in any case does nothing with it's start and end
> variables.
>
> So I think this patch suits us just fine.
umm, OK, well what is the spec for this new interface which Martin
is proposing to add?
It _seems_ to be that if the arch implements tlb_flush_mmu() then its
tlb_finish_mmu() can (should) be a no-op?
Or if the arch's tlb_finish_mmu() does a full mm "flush" (god I hate that
term - here we meant writeback, and perhaps invalidate??)) then its
tlb_flush_mmu() can (should) be a no-op.
Or something like that. Martin, I'd suggest that an update to
Documentation/cachetlb.txt is in order, spell this all out.
Doing this properly would require that Documentation/cachetlb.txt say
something about tlb_gather_mmu() and tlb_finish_mmu() too, I guess.
Please ;)
next prev parent reply other threads:[~2007-07-17 21:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 7:48 + sparc64-rename-tlb_flush_mmu.patch added to -mm tree akpm
[not found] ` <20070717005551.cdb9504e.akpm@linux-foundation.org>
[not found] ` <20070717010324.833fee7e.akpm@linux-foundation.org>
2007-07-17 13:56 ` Martin Schwidefsky
2007-07-17 18:18 ` Russell King
2007-07-17 19:08 ` Andrew Morton
2007-07-17 21:14 ` Russell King
2007-07-17 21:42 ` Andrew Morton [this message]
2007-07-18 7:48 ` Martin Schwidefsky
2007-07-17 21:55 ` Luck, Tony
2007-07-17 22:04 ` Russell King
2007-07-17 22:21 ` Luck, Tony
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=20070717144245.7760a716.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-arch@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.