From: Andrew Morton <akpm@osdl.org>
To: Jack Steiner <steiner@sgi.com>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - Reduce TLB flushing during process migration
Date: Thu, 24 Jun 2004 11:44:49 -0700 [thread overview]
Message-ID: <20040624114449.47fe2f67.akpm@osdl.org> (raw)
In-Reply-To: <20040624125544.GA15742@sgi.com>
Jack Steiner <steiner@sgi.com> wrote:
>
> On Wed, Jun 23, 2004 at 02:33:18PM -0700, Andrew Morton wrote:
> > Jack Steiner <steiner@sgi.com> wrote:
> > >
> > > This patch adds a platform specific hook to allow an arch-specific
> > > function to be called after an explicit migration.
> >
> > OK by me. David, could you please merge this up?
> >
> > Jack, please prepare an update for Documentation/cachetlb.txt.
>
>
> ...
> +7) void tlb_migrate_finish(struct mm_struct *mm)
> +
> + This interface is called at the end of an explicit
> + process migration. This interface provides a hook
> + to allow a platform to update TLB or context-specific
> + information for the address space.
> +
> + The ia64 sn2 platform is one example of a platform
> + that uses this interface.
Ok... But the code is still calling flush_tlb_mm() from within
set_cpus_allowed() on non-ia64 platforms, which I believe is unnecessary.
And it's calling it with a null pointer for kernel threads, which oopses on
i386. We went over this weeks ago.
Shouldn't asm-generic.h be doing
#define tlb_migrate_finish(mm) do {} while (0)
?
next prev parent reply other threads:[~2004-06-24 18:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:38 [PATCH] - Reduce TLB flushing during process migration Jack Steiner
2004-06-23 21:33 ` Andrew Morton
2004-06-24 12:55 ` Jack Steiner
2004-06-24 18:44 ` Andrew Morton [this message]
2004-06-25 14:23 ` Jack Steiner
2004-06-26 5:10 ` David Mosberger
2004-07-02 17:39 ` Jack Steiner
2004-07-07 0:01 ` David Mosberger
2004-07-07 13:52 ` John Richard Moser
2004-07-07 15:48 ` Jack Steiner
2004-07-07 18:30 ` David Mosberger
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=20040624114449.47fe2f67.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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