linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fortescue <mark@mtfhpc.demon.co.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-mm@kvack.org, wli@holomorphy.com, linuxppc-dev@ozlabs.org,
	andrea@suse.de, sparclinux@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>
Subject: Re: vm changes from linux-2.6.14 to linux-2.6.15
Date: Wed, 9 May 2007 20:44:31 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0705092005060.29444@mtfhpc.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0705012354290.12808@mtfhpc.demon.co.uk>

Hi Ben,

Is it worth formally sending in either of my patches or does more work 
need to be done first?

If you would like me to test any changes, it takes me app. 2 hours to 
cross-compile a sparc kernel for my sun4c. I use my sparc system as a 
diskless client with a very minimal setup to alow me to test cross 
compiled GCC and any small platform independent code I may be working on.

I have not yet tried to get linux-2.6.21 or later working but for the test 
setup I have been using, it should not take too long if that is the kernel 
needed for testing.

I may also be able to do the same testing on an embedded PowerPC (32bit) 
(it will need some work to get my cross compilation system working again 
as some kernel changes in the ppc/powerpc architechture have proven to be 
incompatible with my build scripts) and on x86_64/ix86. Once I have fixed 
the build scripts, it will take app. 4 to 6 hours to get the initial NFS 
root minimal system built for these additional architectures and then app. 
2 hours for each test kernel build.

If a simple ADA build is not considered a suficiently harsh test, then I 
could cross compile a specialist test application, if one is available, or 
compile a more extensive application (maybe gcc) on the test system. The 
problem of compiling a more extensive application on the sparc system is 
that it is a slow system running as a diskless client with its NFS root on 
an aging i486 over a 10MBit Ethernet. The result is it will take days to 
compile somthing like gcc.

Regards
 	Mark Fortescue

On Wed, 2 May 2007, Mark Fortescue wrote:

>
>
> On Wed, 2 May 2007, Benjamin Herrenschmidt wrote:
>
>> 
>>> I have attached a patch (so pine does not mangle it) for linux-2.6.20.9.
>>> Is this what you had in mind?
>>> 
>>> For linux-2.6.21, more work will be needed as it has more code calling
>>> ptep_set_access_flags.
>> 
>> I'm not 100% sure we need the 'update' argument... we can remove the
>> whole old_entry, pte_same, etc... and just have pte_set_access_flags()
>> read the old PTE and decide wether something needs to be changed or not.
>> 
>> Ben.
>> 
>> 
>
> The attached patch works on sun4c (with my simple ADA compile test) but the 
> change in functionality may break things other platforms.
>
> The advantage of the previous patch is that the functionality is only changed 
> for sparc sun4c so less testing would be required.
>
> Regards
> 	Mark Fortescue.

  reply	other threads:[~2007-05-09 19:44 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
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 [this message]
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=Pine.LNX.4.61.0705092005060.29444@mtfhpc.demon.co.uk \
    --to=mark@mtfhpc.demon.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=andrea@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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).