linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ollie Wild <aaw@google.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	linux-kernel@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
	linux-arch@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andi Kleen <ak@suse.de>
Subject: Re: [patch] removes MAX_ARG_PAGES
Date: Wed, 9 May 2007 21:04:42 -0400	[thread overview]
Message-ID: <200705092104.43353.rob@landley.net> (raw)
In-Reply-To: <20070509134815.81cb9aa9.akpm@linux-foundation.org>

On Wednesday 09 May 2007 4:48 pm, Andrew Morton wrote:
> On Sun, 6 May 2007 01:51:34 -0700
> "Ollie Wild" <aaw@google.com> wrote:
> 
> > A while back, I sent out a preliminary patch
> > (http://thread.gmane.org/gmane.linux.ports.hppa/752) to remove the
> > MAX_ARG_PAGES limit on command line sizes.  Since then, Peter Zijlstra
> > and I have fixed a number of bugs and addressed the various
> > outstanding issues.
> > 
> > The attached patch incorporates the following changes:
> > 
> > - Fixes a BUG_ON() assertion failure discovered by Ingo Molnar.
> > - Adds CONFIG_STACK_GROWSUP (parisc) support.
> > - Adds auditing support.
> > - Reverts to the old behavior on architectures with no MMU.
> > - Fixes broken execution of 64-bit binaries from 32-bit binaries.
> > - Adds elf_fdpic support.
> > - Fixes cache coherency bugs.
> > 
> > We've tested the following architectures: i386, x86_64, um/i386,
> > parisc, and frv.  These are representative of the various scenarios
> > which this patch addresses, but other architecture teams should try it
> > out to make sure there aren't any unexpected gotchas.
>
> I'll duck this for now, given the couple of problems which people have
> reported. 

Just FYI, a really really quick and dirty way of testing this sort of thing on 
more architectures and you're likely to physically have?

1) Install QEMU.

2) Grab http://landley.net/code/firmware (releases in the downloads directory, 
or tarball of most recent repository snapshot is 
wget "http://landley.net/hg/firmware?ca=tip;type=gz").

3) Edit "download.sh" to point at the URL of your tarball instead of whatever 
kernel.org version it's using.  (Or add your patch to sources/patches if it 
applies to the version it's already using.  Note that if you set SHA1= blank 
in download.sh it'll skip the checksum test, so you don't have to recalculate 
the sha1sum if you don't want to.)

4) Run ./build.sh for the architecture you're interested in.  (I suggest 
armv4l, i686, mipsel, and x86_64.  Both sparc and ppc are currently broken 
for different reasons; I'm working on it.)  Wait a longish time for it to 
finish compiling. :)

5) "cd build; ./run-armv4l.sh" and your shell prompt should now be in qemu 
running a kernel for the appropriate architecture.  (You even have a native 
version of gcc you can build stuff with, although you may have 
to "ln -s /tools/lib /lib" to run the results, for reasons Linux From Scratch 
developers will recognize. :)

This won't help you test real hardware (at least hardware qemu doesn't 
emulate), but for stuff like filesystems or executable file formats, it's 
handy. :)

Email me if something doesn't work...

Rob

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-05-10  1:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06  8:51 Ollie Wild
2007-05-07 17:46 ` Luck, Tony
2007-05-07 19:01   ` William Lee Irwin III
2007-05-22 12:24   ` Peter Zijlstra
2007-05-22 23:49     ` Luck, Tony
2007-05-24 15:20       ` Peter Zijlstra
2007-05-25 18:48         ` Luck, Tony
2007-05-09 20:48 ` Andrew Morton
2007-05-10  1:04   ` Rob Landley [this message]
2007-05-10  4:06     ` Ollie Wild
2007-05-10  9:19       ` Rob Landley

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=200705092104.43353.rob@landley.net \
    --to=rob@landley.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=aaw@google.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=parisc-linux@lists.parisc-linux.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