From: Michael Shalayeff <mickey@lucifier.dial-up.user.akula.net>
To: sieler@allegro.com (Stan Sieler)
Subject: Re: [hppa-linux] syscall work
Date: Mon, 29 Mar 1999 16:55:07 -0500 (EST) [thread overview]
Message-ID: <199903292200.RAA12330@lucifier.dial-up.user.akula.net> (raw)
In-Reply-To: <199903292146.NAA28577@bart.allegro.com> from Stan Sieler at "Mar 29, 99 01:46:02 pm"
Making, drinking tea and reading an opus magnum from Stan Sieler:
> Hi,
re
> > okie, but why emulating gate instruction, when there is already such
> > instruction exist? (;
>
> Simple: HP does this...there must be a reason.
>
> They appear to do it on selected models of PA-RISC systems. Why? Don't know.
which models? could it be level 1 systems w/ less VM resources?
> I can only conjecture...and the conjecture is the obvious one: there must be
> some circumstance where GATE fails. Otherwise, *why* replace it with
> a slightly slower mechanism?
hardware bug for example? maybe again on certain systems w/ less
tlb size and/or cache.
btw, lites/mklinux do not emulate gate.
cu
--
paranoic mickey (my employers have changed but, the name has remained)
next parent reply other threads:[~1999-03-29 22:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199903292146.NAA28577@bart.allegro.com>
1999-03-29 21:55 ` Michael Shalayeff [this message]
1999-03-29 21:50 [hppa-linux] syscall work Stan Sieler
-- strict thread matches above, loose matches on Subject: below --
1999-03-25 23:40 Bjorn Helgaas
1999-03-26 0:42 ` Alan Cox
1999-03-25 20:46 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
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
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=199903292200.RAA12330@lucifier.dial-up.user.akula.net \
--to=mickey@lucifier.dial-up.user.akula.net \
--cc=mickey@openbsd.org \
--cc=sieler@allegro.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