From: Mike Shaver <shaver@netscape.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] Gateway instructions
Date: Thu, 18 Mar 1999 16:51:09 -0500 [thread overview]
Message-ID: <36F1754D.17EA4048@netscape.com> (raw)
In-Reply-To: 199903181840.KAA25312@cllmail.cup.hp.com
Cary Coutant wrote:
> When a page's access rights are 4, 5, 6, or 7, a gateway instruction on
> that page causes the privilege promotion. Most HP-UX system calls are
> branches to a common gateway instruction on a gateway page in the fourth
> quadrant. This gateway instruction then branches to a common syscall
> entry sequence that ultimately switches on the syscall number passed in a
> GR. Some "lightweight" syscalls may be implemented with their own
> gateways.
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.
I presume that the syscall gateway page layout is part of the HP-UX
kernel/user ABI though, so we'll be following your lead for SOM/HP-ELF
binaries anyway.
> The B bit is not a problem as long as the delay slot of the branch to the
> gateway is either nullified or filled in with a non-branch instruction.
> For example,
>
> LDIL L'GATEWAY,%r1
> BLE R'GATEWAY(%sr7,%r1)
> LDO sycallnum,%r22
Someday (maybe today, if I get all my work done =) ), I'll learn to read
that.
Mike
--
368177.00 314980.91
next prev parent reply other threads:[~1999-03-18 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-18 18:43 [hppa-linux] Gateway instructions Cary Coutant
1999-03-18 21:51 ` Mike Shaver [this message]
1999-03-19 15:40 ` Kumar
-- strict thread matches above, loose matches on Subject: below --
1999-03-19 1:38 Cary Coutant
1999-03-19 6:10 ` Mike Shaver
1999-03-19 6:58 ` Mike Shaver
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=36F1754D.17EA4048@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 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.