From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org,
Andrea Arcangeli <andrea@suse.de>,
wli@holomorphy.com, linux-mm@kvack.org
Subject: Re: vm changes from linux-2.6.14 to linux-2.6.15
Date: Mon, 30 Apr 2007 14:54:14 -0700 [thread overview]
Message-ID: <20070430145414.88fda272.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0704302159140.3178@mtfhpc.demon.co.uk>
On Mon, 30 Apr 2007 22:36:27 +0100 (BST)
Mark Fortescue <mark@mtfhpc.demon.co.uk> wrote:
> Hi all,
>
> I have tracked down a failure to successfully load/run the init task on my
> Sparcstation 1 clone (SS1) and Sparcstation 2 (SS2), sparc32 sun4c
> systems, to a patch:
>
> commit 1a44e149084d772a1bcf4cdbdde8a013a8a1cfde.
> [PATCH] .text page fault SMP scalability optimization
>
> Removing this patch fixes the issue and allows me to use kernels later
> than v2.5.14. (tested using linux-2.6.20.9).
>
> Given the comment provided by the git bisect, backing out this patch will
> probably have undesirable conseqnences for other platforms (especially
> powerpc64) so, if an architecture independent solution is not available,
> some/all of the code in handle_pte_fault() in mm/memory.c will need be to
> made architecture dependent.
>
> I am not sufficiently familear with the how the SS1/SS2 mmu works and how
> the linux memory management system works to understand why this patch
> prevents my sun4c SS1/SS2 systems from working.
>
> Advice and help on the approch to take and any code changes regarding this
> issue would be most welcome.
>
Interesting - thanks for working that out. Let's keep linux-mm on cc please.
next prev parent reply other threads:[~2007-04-30 21:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0704291345480.690@mtfhpc.demon.co.uk>
[not found] ` <1177852457.4390.26.camel@localhost.localdomain>
2007-04-30 21:36 ` vm changes from linux-2.6.14 to linux-2.6.15 Mark Fortescue
2007-04-30 21:54 ` Andrew Morton [this message]
2007-04-30 22:04 ` David Miller
2007-04-30 22:33 ` Mark Fortescue
2007-04-30 22:42 ` David Miller
2007-05-01 0:00 ` Benjamin Herrenschmidt
2007-05-01 0:38 ` David Miller
2007-05-01 1:45 ` Mark Fortescue
2007-05-01 2:05 ` Benjamin Herrenschmidt
2007-05-01 13:58 ` Mark Fortescue
2007-05-01 21:31 ` Benjamin Herrenschmidt
2007-05-01 23:08 ` Mark Fortescue
2007-05-09 19:44 ` Mark Fortescue
2007-05-09 22:48 ` Benjamin Herrenschmidt
2007-05-10 6:19 ` Andrew Morton
2007-05-10 6:29 ` Benjamin Herrenschmidt
2007-05-10 7:12 ` David Miller
2007-05-14 19:19 ` Hugh Dickins
2007-05-14 21:07 ` Benjamin Herrenschmidt
2007-05-15 6:56 ` Benjamin Herrenschmidt
2007-05-21 14:27 ` Tom "spot" Callaway
2007-05-21 22:09 ` Benjamin Herrenschmidt
2007-05-22 6:28 ` [PATCH/RFC] Rework ptep_set_access_flags and fix sun4c Benjamin Herrenschmidt
2007-05-22 17:04 ` Hugh Dickins
2007-05-22 22:59 ` Benjamin Herrenschmidt
2007-05-22 23:04 ` Tom "spot" Callaway
2007-05-23 4:03 ` Hugh Dickins
2007-05-23 4:21 ` Benjamin Herrenschmidt
2007-05-22 21:52 ` Mark Fortescue
2007-05-22 21:53 ` David Miller
2007-05-22 23:29 ` Benjamin Herrenschmidt
2007-05-22 23:28 ` Benjamin Herrenschmidt
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=20070430145414.88fda272.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).