linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ollie Wild <aaw@google.com>,
	linux-kernel@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
	linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>
Subject: RE: [patch] removes MAX_ARG_PAGES
Date: Tue, 22 May 2007 16:49:02 -0700	[thread overview]
Message-ID: <617E1C2C70743745A92448908E030B2A0184DF88@scsmsx411.amr.corp.intel.com> (raw)
In-Reply-To: <1179836645.7019.86.camel@twins>

> In order to solve this, I added a STACK_TOP_MAX macro for each arch and
> use that. This made IA64 boot properly.

Yes.  Patches apply to 2.6.21 cleanly, build cleanly and boot for me too.
I can even run:

	$ ls -lrt `find /usr/share -type f -print`

on the new kernel (thats 48020 files for a total of 2.3MB of args).

> The second patch makes the compat stuff compile, untested though, as I
> have no idea how that works on ia64.

Not so good on this part.  Running an ia32 binary on this patched kernel
just hung my system :-(

-Tony



  reply	other threads:[~2007-05-22 23:49 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 [this message]
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
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=617E1C2C70743745A92448908E030B2A0184DF88@scsmsx411.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=aaw@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.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