public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Matthew Wilcox <willy@debian.org>
Cc: ak@suse.de, linux-arch@vger.kernel.org, carlos@baldric.uwo.ca
Subject: Re: compat-signal-noarch-2004-01-29.patch again
Date: Sat, 20 Mar 2004 12:20:48 -0800	[thread overview]
Message-ID: <20040320122048.70db9888.akpm@osdl.org> (raw)
In-Reply-To: <20040320133634.GU25059@parcelfarce.linux.theplanet.co.uk>

Matthew Wilcox <willy@debian.org> wrote:
>
> On Sat, Mar 20, 2004 at 05:57:53AM +0100, Andi Kleen wrote:
> > No. The problem is not in a particular implementation of this for a specific 
> > architecture, but in the generic design - it is the wrong direction and will
> > cause hard to fix later design problems.
> 
> You're wrong.  Just accept this patch.

I can sort-of-see Andi's worry.

The issue appears to be that at some time in the future he will have 64-bit
applications using the 32-bit API without PER_LINUX32 set.  So the proposed
is_compat_task() is meaningless in this context - hence Andi doesn't want
is_compat_task() propagated around the place.

This begs the question of how his kernel correctly handle these
pseudo-32-bit tasks.

  reply	other threads:[~2004-03-20 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20  5:49 compat-signal-noarch-2004-01-29.patch again Andrew Morton
2004-03-20  4:15 ` Andi Kleen
2004-03-20  6:37   ` Andrew Morton
2004-03-20  4:57     ` Andi Kleen
2004-03-20  7:42       ` Andrew Morton
2004-03-20 13:36       ` Matthew Wilcox
2004-03-20 20:20         ` Andrew Morton [this message]
2004-03-20 20:29           ` Matthew Wilcox
2004-03-20 20:31           ` James Bottomley

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=20040320122048.70db9888.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=carlos@baldric.uwo.ca \
    --cc=linux-arch@vger.kernel.org \
    --cc=willy@debian.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