Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Cary Coutant <cary@cup.hp.com>
To: <hppa-linux@thepuffingroup.com>
Subject: Re: [hppa-linux] Gateway instructions
Date: Thu, 18 Mar 1999 17:38:28 -0800	[thread overview]
Message-ID: <199903190135.RAA15176@cllmail.cup.hp.com> (raw)

>OK, so you don't have a spot on the page for each syscall?  I was
>thinking that we'd want to do that, since we're going to use the whole
>page anyway and it would make things a little quicker by eliminating the
>later dispatch-by-syscall step.

There's a fair amount of setup code common to all syscalls before the 
dispatch to individual kernel entry points, and there are a lot of 
syscalls in HP-UX, so we use a single gateway.

For the 64-bit ABI, the gateway address is not hardcoded; when the 
program is loaded, the kernel passes it the address of a syscall vector 
table, which has one pointer per syscall. Most of the syscalls still 
vector to the one common gateway, but the lightweight syscalls can now be 
vectored off to a special gateway that has less overhead.

The 32-bit syscall convention is documented in (of all places) the 
Assembler manual; the 64-bit convention is documented in the PA-64 
runtime supplement (program startup chapter). These documents are 
available from

    http://www.software.hp.com/STK


Cary Coutant
Hewlett-Packard Co.
Application Delivery Lab

             reply	other threads:[~1999-03-19  1:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-19  1:38 Cary Coutant [this message]
1999-03-19  6:10 ` [hppa-linux] Gateway instructions Mike Shaver
1999-03-19  6:58   ` Mike Shaver
  -- strict thread matches above, loose matches on Subject: below --
1999-03-18 18:43 Cary Coutant
1999-03-18 21:51 ` Mike Shaver
1999-03-19 15:40   ` Kumar
1999-03-18 17:34 Bjorn Helgaas
1999-03-18 14:35 Christopher Neufeld
1999-03-18 16:55 ` Mike Shaver
1999-03-18 18:05   ` Alan Cox

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=199903190135.RAA15176@cllmail.cup.hp.com \
    --to=cary@cup.hp.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