All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-kernel@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
	linux-arch@vger.kernel.org
Cc: Ollie Wild <aaw@google.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	Andi Kleen <ak@suse.de>
Subject: [PATCH 0/4] no MAX_ARG_PAGES
Date: Tue, 05 Jun 2007 17:05:23 +0200	[thread overview]
Message-ID: <20070605150523.786600000@chello.nl> (raw)


This patch-set aims at removing the current limit on argv+env space aka.
MAX_ARG_PAGES.

The new mm is created before the binfmt code runs, the stack is placed at the
highest address supported by that architecture.

The argv+env data is then copied from the old mm into the new mm (which is
inactive at that time - this introduces some cache coherency issues).

Then we run the binfmt code, which will compute the final stack address. The
existing stack will be moved downwards (or upwards on PA-RISC) to the desired
place.

This 'trick' heavily relies on the MMU, so for no-MMU archs we stay with the
old approach.

Tested-on: i386, ia64, frv, parisc, ppc64, um, x86_64

Patches against: .22-rc4

-- 
Changes since last time:

 - fixed ia64
     ( va-space constraints )

 - fixed ia64 CONFIG_IA32_SUPPORT
     ( brown paper bags and more va-space constraints)

 - fixed powerpc
     ( address limit on stack extention )

 - removed audit_kill() in favour of audit_panic()

 - nicely spit out the patches


WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-kernel@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
	linux-arch@vger.kernel.org
Cc: Ollie Wild <aaw@google.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
	Andi Kleen <ak@suse.de>
Subject: [PATCH 0/4] no MAX_ARG_PAGES
Date: Tue, 05 Jun 2007 17:05:23 +0200	[thread overview]
Message-ID: <20070605150523.786600000@chello.nl> (raw)

This patch-set aims at removing the current limit on argv+env space aka.
MAX_ARG_PAGES.

The new mm is created before the binfmt code runs, the stack is placed at the
highest address supported by that architecture.

The argv+env data is then copied from the old mm into the new mm (which is
inactive at that time - this introduces some cache coherency issues).

Then we run the binfmt code, which will compute the final stack address. The
existing stack will be moved downwards (or upwards on PA-RISC) to the desired
place.

This 'trick' heavily relies on the MMU, so for no-MMU archs we stay with the
old approach.

Tested-on: i386, ia64, frv, parisc, ppc64, um, x86_64

Patches against: .22-rc4

-- 
Changes since last time:

 - fixed ia64
     ( va-space constraints )

 - fixed ia64 CONFIG_IA32_SUPPORT
     ( brown paper bags and more va-space constraints)

 - fixed powerpc
     ( address limit on stack extention )

 - removed audit_kill() in favour of audit_panic()

 - nicely spit out the patches

--
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-06-05 15:14 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 15:05 Peter Zijlstra [this message]
2007-06-05 15:05 ` [PATCH 0/4] no MAX_ARG_PAGES Peter Zijlstra
2007-06-05 15:05 ` [PATCH 1/4] arch: personality independent stack top Peter Zijlstra
2007-06-05 15:05   ` Peter Zijlstra
2007-06-05 15:05 ` [parisc-linux] " Peter Zijlstra
2007-06-05 15:05 ` [PATCH 2/4] audit: rework execve audit Peter Zijlstra
2007-06-05 15:05   ` Peter Zijlstra
2007-06-05 15:05   ` Peter Zijlstra
2007-06-05 23:39   ` Andrew Morton
2007-06-05 23:39     ` Andrew Morton
2007-06-05 23:39     ` Andrew Morton
2007-06-06  5:52     ` Peter Zijlstra
2007-06-06  5:52       ` Peter Zijlstra
2007-06-06  5:52       ` Peter Zijlstra
2007-06-05 15:05 ` [parisc-linux] " Peter Zijlstra
2007-06-05 15:05 ` [PATCH 3/4] mm: move_page_tables{,_up} Peter Zijlstra
2007-06-05 15:05   ` Peter Zijlstra
2007-06-05 19:46   ` Christoph Lameter
2007-06-05 19:46     ` Christoph Lameter
2007-06-05 23:39   ` Andrew Morton
2007-06-05 23:39     ` Andrew Morton
2007-06-06 19:06   ` Ollie Wild
2007-06-06 19:06     ` Ollie Wild
2007-06-06 19:12     ` Peter Zijlstra
2007-06-06 19:12       ` Peter Zijlstra
2007-06-06 19:50       ` Ollie Wild
2007-06-06 19:50         ` Ollie Wild
2007-06-06 19:53         ` Peter Zijlstra
2007-06-06 19:53           ` Peter Zijlstra
2007-06-05 15:05 ` [parisc-linux] " Peter Zijlstra
2007-06-05 15:05 ` [PATCH 4/4] mm: variable length argument support Peter Zijlstra
2007-06-05 15:05   ` Peter Zijlstra, Ollie Wild
2007-06-05 23:39   ` Andrew Morton
2007-06-05 23:39     ` Andrew Morton
2007-06-06  0:48     ` Ollie Wild
2007-06-06  0:48       ` Ollie Wild
2007-06-06  6:02     ` Peter Zijlstra
2007-06-06  6:02       ` Peter Zijlstra
2007-06-06  8:36   ` Andrew Morton
2007-06-06  8:36     ` Andrew Morton
2007-06-06  8:44     ` Paul Mundt
2007-06-06  8:44       ` Paul Mundt
2007-06-06  8:54     ` Peter Zijlstra
2007-06-06  8:54       ` Peter Zijlstra
2007-06-06  9:06       ` Andrew Morton
2007-06-06  9:06         ` Andrew Morton
2007-06-06  9:12         ` Peter Zijlstra
2007-06-06  9:12           ` Peter Zijlstra
2007-06-06 14:40           ` [parisc-linux] " Grant Grundler
2007-06-06 14:40             ` Grant Grundler
2007-06-06  9:34         ` Peter Zijlstra
2007-06-06  9:34           ` Peter Zijlstra
2007-06-06  9:44           ` Paul Mundt
2007-06-06  9:44             ` Paul Mundt
2007-06-06  9:47             ` Peter Zijlstra
2007-06-06  9:47               ` Peter Zijlstra
2007-06-06  9:53               ` Andi Kleen
2007-06-06  9:53                 ` Andi Kleen
2007-06-05 15:05 ` [parisc-linux] " Peter Zijlstra

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=20070605150523.786600000@chello.nl \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.