From: Mike Shaver <shaver@netscape.com>
To: hppa-linux@thepuffingroup.com
Subject: Re: [hppa-linux] syscall work
Date: Thu, 25 Mar 1999 18:55:47 -0500 [thread overview]
Message-ID: <36FACD03.6446ACF4@netscape.com> (raw)
In-Reply-To: 36FAC708.362B@cup.hp.com
Bob Pflederer wrote:
>
> > 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.
>
> Isn't the next page at 0xc0001000? Or does linux have some concept of
> 1k "pages" even though pages in the TLB are 4k?
Brain-o. 0xC0001004 it is.
While we're on the topic, though: why 0xC0000004 and not 0xC0000000 as
the target address? (Although there are other bugs, like ``ldo 5,%r22''
instead of ``ldi 5,%r22'' in the Assembler Ref as well, so maybe this is
another?)
Mike
--
92501.80 83731.86
next prev parent reply other threads:[~1999-03-25 23:56 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 [this message]
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=36FACD03.6446ACF4@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.