public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Linux Arch list <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] set_pte() part 2 arch usage
Date: Tue, 01 Mar 2005 12:45:28 +1100	[thread overview]
Message-ID: <1109641528.15027.283.camel@gaston> (raw)
In-Reply-To: <20050226211910.79dbfa45.davem@davemloft.net>

On Sat, 2005-02-26 at 21:19 -0800, David S. Miller wrote:
> On Sat, 26 Feb 2005 19:09:43 -0800
> "David S. Miller" <davem@davemloft.net> wrote:
> 
> > I know of at least three such cases so far, vmalloc.c:unmap_area_pte(),
> > vmalloc.c:map_area_pte(), and mprotect.c:change_pte_range()
> > 
> > The latter could definitely explain the behavior you are seeing on
> > ppc64.
> 
> Ok, here's a fix, let me know if it makes the PPC64 problems
> go away Ben.

Test machine has been LTP'ing happily over night with that patch.

Ben.

  reply	other threads:[~2005-03-01  1:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24  4:07 [PATCH] set_pte() part 2 arch usage David S. Miller
2005-02-24  5:18 ` Benjamin Herrenschmidt
2005-02-24 22:36   ` David S. Miller
2005-02-25  5:32     ` Benjamin Herrenschmidt
2005-02-25  7:20       ` Benjamin Herrenschmidt
2005-02-25  7:57         ` David S. Miller
2005-02-25 18:37         ` David S. Miller
2005-02-26  0:56           ` Benjamin Herrenschmidt
2005-02-27  3:09             ` David S. Miller
2005-02-27  5:19               ` David S. Miller
2005-03-01  1:45                 ` Benjamin Herrenschmidt [this message]
2005-03-01 23:02                   ` David S. Miller
2005-03-01  2:22                 ` Benjamin Herrenschmidt
2005-03-01 23:32                   ` David S. Miller
2005-02-27  9:35               ` Benjamin Herrenschmidt
2005-02-28  4:14                 ` David S. Miller

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=1109641528.15027.283.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-arch@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