All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ian Kent <raven@themaw.net>, David Miller <davem@davemloft.net>,
	thomas@m3y3r.de, linux-kernel@vger.kernel.org
Subject: Re: Linux 3.3-rc4
Date: Mon, 20 Feb 2012 21:27:03 -0800	[thread overview]
Message-ID: <4F432B27.4000708@zytor.com> (raw)
In-Reply-To: <CA+55aFzcWjPrK4csbThuGimt6bHC+bcgFhj-r8d3M1MxhN_HKg@mail.gmail.com>

On 02/20/2012 09:21 PM, Linus Torvalds wrote:
> On Mon, Feb 20, 2012 at 9:06 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> So it really is limited to only x86.
> 
> Oh, and if people really are using "uname()" to figure out that they
> are running a 64-bit kernel, then we should probably make uname() use
> "is_compat_task()" instead of checking the PER_LINUX32 personality.
> 
> So we already do have support for returning a different machine-name
> to 32-bit binaries, but it uses the "personality" thing that nobody
> cares about, rather than the compat layer. Looks like purely
> historical reasons.
> 

No, it serves a real function.  I use both directions of this to deal
with various compatibility things.  PER_LINUX32 lets you run, say, an
installer as if it was on a 32-bit program, even if it is written in a
scripting language (and hence running a native 64-bit interpreter).
Similarly, a 32-bit legacy binary can still function as part of a bigger
64-bit system.

So let's not change that just because someone did something idiotic.

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-02-21  5:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19  0:27 Linux 3.3-rc4 Linus Torvalds
2012-02-19 13:42 ` Thomas Meyer
2012-02-19 18:45   ` Linus Torvalds
2012-02-19 19:49     ` David Miller
2012-02-19 20:02       ` Linus Torvalds
2012-02-20  3:28         ` Ian Kent
2012-02-21  3:29         ` Ian Kent
2012-02-21  3:38           ` Linus Torvalds
2012-02-21  4:02             ` Ian Kent
2012-02-21  4:17               ` Linus Torvalds
2012-02-21  4:52                 ` Ian Kent
2012-02-21  5:06                   ` Linus Torvalds
2012-02-21  5:21                     ` Linus Torvalds
2012-02-21  5:27                       ` H. Peter Anvin [this message]
2012-02-21  5:28                     ` H. Peter Anvin
2012-02-21  5:32                       ` Linus Torvalds
2012-02-21  5:39                     ` Ian Kent
2012-02-21  4:18           ` H. Peter Anvin
2012-02-21  4:22         ` H. Peter Anvin
2012-02-21 13:03           ` Alan Cox
2012-02-21 18:26             ` Use gcc to check exported files [Was: Linux 3.3-rc4] Sam Ravnborg
2012-02-21 18:58     ` Linux 3.3-rc4 Thomas Meyer
2012-02-21 22:07       ` Linus Torvalds
2012-02-21 22:43   ` Linus Torvalds
2012-02-21 23:10     ` Eric Dumazet
2012-02-21 23:19       ` Linus Torvalds
2012-02-24 10:39 ` Jiri Kosina
2012-02-24 16:52   ` Linus Torvalds
2012-02-24 18:01     ` Jiri Kosina
2012-02-24 18:21       ` Linus Torvalds
2012-02-29  8:38       ` Jiri Kosina

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=4F432B27.4000708@zytor.com \
    --to=hpa@zytor.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raven@themaw.net \
    --cc=thomas@m3y3r.de \
    --cc=torvalds@linux-foundation.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.