Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Stan Sieler <sieler@allegro.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HPUX binary compatibility
Date: Mon, 21 Jun 1999 11:07:19 -0700 (PDT)	[thread overview]
Message-ID: <199906211807.LAA29277@bart.allegro.com> (raw)
In-Reply-To: <14480.929987303@upchuck.cygnus.com> from "Jeffrey A Law" at Jun 21, 99 11:48:23 am

Jeff writes:

>   > The problem with translators is that they don't work in all cases.
>   > 
>   > The most important case is where you want to link some .o files
>   > together: some are compiled for Linux, some for HP-UX. 
>   > 
>   > *That's* why having different system call numbers is important.

> You really don't want to do that.  I strongly recommend against it.  In

(Presuming "that" is "have different system call numbers")

> 5 years of working on a system which had hpux compatibility we had zero
> need to do this kind of stuff and it just makes things a lot more complicated
> than they need to be.

You're "compatible" if you can run an HP-UX app "out of the box" (e.g.,
restore it and run).  If you have to run it through a translator of some kind,
you aren't compatible.   (If the translator is part of the OS, and invoked 
automatically & invisibly, that's ok...been there, used that for 15 years 
on MPE)

So...how do you achieve this level of compatibility?  Simple...the HP-UX
system call numbers *must* be honored.  What does that mean, then, if
Linux has an identically named (not numbered) system call whose
semantics differ?  Precisely one thing: the kernel must be able to
differentiate between them.  There are two basic methods of doing this:

  1) different system call numbers

or 

  2) different gateway page for the system calls (e.g., 0xc0000000 for
     HP-UX, and 0xc0000040 for Linux).  (Note: I don't recall the exact
     digits HP-UX uses...the values above are for illustrative purposes)
     (The kernel could check to see which address had been used for the
     call)

Without such a mechanism, you can't tell the system calls apart.

So, the only unanswered question is: is HP-UX compatibility desired?  
If the answer is "yes", the subsequent question (how) was answered above.

-- 
Stan Sieler                                          sieler@allegro.com
                                         http://www.allegro.com/sieler/

  reply	other threads:[~1999-06-21 18:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-20 17:40 [parisc-linux] HPUX binary compatibility Matthew Wilcox
1999-06-20 19:45 ` Stan Sieler
1999-06-20 20:21 ` Jeffrey A Law
1999-06-21  8:50   ` Matthew Wilcox
1999-06-21 15:06     ` [parisc-linux] Assembly error: entry.S John David Anglin
1999-06-21 15:20       ` Matthew Wilcox
1999-06-21 15:27         ` John David Anglin
1999-06-21 15:42           ` Matthew Wilcox
1999-06-21 15:55             ` John David Anglin
1999-06-21 16:07               ` Matthew Wilcox
1999-06-21 16:16                 ` John David Anglin
1999-06-21 16:32             ` [parisc-linux] Hack to head.S John David Anglin
1999-06-21 17:23     ` [parisc-linux] HPUX binary compatibility Stan Sieler
1999-06-21 17:48       ` Jeffrey A Law
1999-06-21 18:07         ` Stan Sieler [this message]
1999-06-21 18:23           ` Jeffrey A Law
1999-06-20 21:05 ` Alan Cox
1999-06-21  8:41   ` Matthew Wilcox
1999-06-21 10:35     ` Alan Cox
1999-06-21 21:39 ` Larry Dwyer
1999-06-22  9:45   ` Matthew Wilcox
1999-06-22  9:49     ` Alan Cox
1999-06-22 10:05       ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
1999-06-21 18:20 Mike Hibler
1999-06-21 20:49 ` Stan Sieler

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=199906211807.LAA29277@bart.allegro.com \
    --to=sieler@allegro.com \
    --cc=parisc-linux@thepuffingroup.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