From: Mike Shaver <shaver@netscape.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] syscall work
Date: Thu, 25 Mar 1999 16:07:33 -0500 [thread overview]
Message-ID: <36FAA595.DB56B012@netscape.com> (raw)
In-Reply-To: 199903252046.OAA08061@helgaaspc.rsn.hp.com
Bjorn Helgaas wrote:
> If Linux uses a different gateway page address than HP-UX (which I
> think is a good idea), why not use a strategy like that used for
> 64-bit HP-UX apps, where the kernel supplies the address in a
> register at application startup?
OK, I'm convinced. I've changed unistd.h to use 0xC0000404 (on the next
page) for the syscall gateway, although we can easily change it back.
The ``Assembly Language Reference Manual'' I have says:
Refer to the /HP-UX Reference/ manual for more information on HP-UX
system
calls.
Anyone know what manual they're talking about? I'd like to find out
what to do for syscalls that take more than 4 arguments, like mmap and
recvfrom and sendto.
Mike
--
81996.85 73813.97
next prev parent reply other threads:[~1999-03-25 21:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-25 20:46 [hppa-linux] syscall work Bjorn Helgaas
1999-03-25 21:07 ` Mike Shaver [this message]
1999-03-25 21:27 ` Stan Sieler
1999-03-25 23:30 ` Bob Pflederer
1999-03-25 23:55 ` Mike Shaver
1999-03-26 5:01 ` Kumar
1999-03-29 4:08 ` Stan Sieler
1999-03-26 15:39 ` Michael Shalayeff
1999-03-26 11:12 ` Mike Shaver
1999-03-26 17:03 ` Michael Shalayeff
1999-03-29 21:27 ` Stan Sieler
1999-03-29 20:41 ` Michael Shalayeff
[not found] <199903292146.NAA28577@bart.allegro.com>
1999-03-29 21:55 ` Michael Shalayeff
-- strict thread matches above, loose matches on Subject: below --
1999-03-29 21:50 Stan Sieler
1999-03-25 23:40 Bjorn Helgaas
1999-03-26 0:42 ` Alan Cox
1999-03-25 19:23 Cary Coutant
1999-03-25 20:12 ` Mike Shaver
1999-03-25 23:05 ` Alan Cox
1999-03-25 17:33 Mike Shaver
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=36FAA595.DB56B012@netscape.com \
--to=shaver@netscape.com \
--cc=hppa-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