From: Stan Sieler <sieler@allegro.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] syscall work
Date: Sun, 28 Mar 1999 20:08:15 -0800 (PST) [thread overview]
Message-ID: <199903290408.UAA29047@bart.allegro.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990325205652.197B-100000@quark.ix.netcom.com> from "Kumar" at Mar 25, 99 09:01:05 pm
Hi,
There may be a reason to avoid the GATE instruction...I've seen some
HP PA-RISC systems where GATE has given way to simply
marking the "gateway" page as non-executable, and relying on a trap
handler to detect the gateway access. The final result is the same...
an architected method of doing a system call. (I can only conjecture
that there is a reason for this...but I don't know what it is.)
Perhaps we can get an HP person to comment?
> It does not matter as long as the gateway instruction is on the "special"
> page. Probably one wants to put a nop before the gateway instruction.
--
Stan Sieler sieler@allegro.com
http://www.allegro.com/sieler.html
next prev parent reply other threads:[~1999-03-29 4: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
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 [this message]
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=199903290408.UAA29047@bart.allegro.com \
--to=sieler@allegro.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