All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: 2.1.126 still no sparc64 autofsu
Date: Sat, 14 Nov 1998 19:53:04 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91108815922574@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91107863319189@msgid-missing>

> 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].

Simple reason: the userland application in question is a 32bit application,
not the native 64bit application, while the kernel is 64bit. 64bit apps
don't need any translations, 32bit apps run in 32bit emulation. So, we are
of course not going to change it to int, just add ioctls playing with that
structure into our 32bit compatibility layer.
> 
> Changing that to "int" would be just fine, *except* it would break the
> protocol for all other platforms.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.127 on a sparc64 machine (498.80 BogoMips).
___________________________________________________________________

  parent reply	other threads:[~1998-11-14 19:53 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 [this message]
1998-11-15  0:52 ` David S. Miller
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-91108815922574@msgid-missing \
    --to=jj@sunsite.ms.mff.cuni.cz \
    --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.