From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.126 still no sparc64 autofsu
Date: Sun, 15 Nov 1998 00:52:51 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91110185427057@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91107863319189@msgid-missing>
From: "H. Peter Anvin" <hpa@transmeta.com>
Date: Sat, 14 Nov 1998 00:17:49 -0800 (PST)
Why is the "long" a different size in kernel and user space? That
seems buggy. It's an easy thing to fix, but it seems like the
Wrong Thing[TM].
Changing that to "int" would be just fine, *except* it would break
the protocol for all other platforms.
All of our userlands currently on sparc64 are 32-bit because we have
not bootstrapped a 64-bit userland fully enough yet.
We have a full (sic) 32-64 bit translation layer for all user visible
interfaces of the kernel already in files named
arch/sparc64/kernel/*32*.c which are supposed to take care of all
these issues. Every once in a while an ioctl() or two slip by without
our noticing and we have to take care of it when the user finally hits
it. :-)
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-11-15 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-14 8:17 2.1.126 still no sparc64 autofsu H. Peter Anvin
1998-11-14 15:45 ` Rich Sahlender
1998-11-14 19:53 ` Jakub Jelinek
1998-11-15 0:52 ` David S. Miller [this message]
1998-11-15 23:49 ` H. Peter Anvin
1998-11-15 23:54 ` David S. Miller
1998-11-16 6:47 ` H. Peter Anvin
1998-11-16 6:48 ` Jakub Jelinek
1998-11-16 7:57 ` Jakub Jelinek
1998-11-16 8:37 ` H. Peter Anvin
1998-11-16 20:33 ` Rich Sahlender
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=marc-linux-ultrasparc-91110185427057@msgid-missing \
--to=davem@dm.cobaltmicro.com \
--cc=ultralinux@vger.kernel.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.