From: Alexander Nyberg <alexn@dsv.su.se>
To: "Zou, Nanhai" <nanhai.zou@intel.com>
Cc: Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>
Subject: RE: [discuss] [Patch] X86_64 TASK_SIZE cleanup - more comments
Date: Sat, 23 Apr 2005 11:10:03 +0200 [thread overview]
Message-ID: <1114247403.916.3.camel@localhost.localdomain> (raw)
In-Reply-To: <894E37DECA393E4D9374E0ACBBE74270013E8B96@pdsmsx402.ccr.corp.intel.com>
> PPC64 IA64 and S390 use variable size TASK_SIZE for 32 bit and 64 bit
> program.
> I feel it is hard to maintain if we try to audit TASK_SIZE use
> everywhere, because most of them are in generic code.
>
> And maintaining those audit code in separate place is also a problem.
> E.g. in current 32 bit emulation code
> TASK_SIZE is defined as 0xfffffff in elf loading, but defined as
> 0xffffe000 in mmaping.
>
> How did that earlier patch break applications?
http://www.ussg.iu.edu/hypermail/linux/kernel/0408.2/1605.html
I never investigated specifically what broke down
next prev parent reply other threads:[~2005-04-23 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 16:09 [discuss] [Patch] X86_64 TASK_SIZE cleanup - more comments Zou, Nanhai
2005-04-23 9:10 ` Alexander Nyberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-27 16:20 Zou, Nanhai
2005-04-20 17:17 [discuss] [Patch] X86_64 TASK_SIZE cleanup Zou, Nanhai
2005-04-21 11:54 ` [discuss] [Patch] X86_64 TASK_SIZE cleanup - more comments Andi Kleen
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=1114247403.916.3.camel@localhost.localdomain \
--to=alexn@dsv.su.se \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=suresh.b.siddha@intel.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