Linux PARISC architecture development
 help / color / mirror / Atom feed
From: David Huggins-Daines <dhd@linuxcare.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Boot error on C200+
Date: 03 Sep 2000 01:16:46 -0400	[thread overview]
Message-ID: <877l8ukqbl.fsf@linuxcare.com> (raw)
In-Reply-To: Ryan Bradetich's message of "Sat, 02 Sep 2000 20:26:31 -0600"

Ryan Bradetich <rbradetich@uswest.net> writes:

> > Note that GR20 is 0x37, which is the syscall number for fcntl(), which
> > confirms your earlier findings :-)
> 
> From arch/parisc/kernel/syscall.S
> 
>         ENTRY_NAME(sys_ioctl)
>         ENTRY_NAME(sys_fcntl)           /* 55 */
>         ENTRY_NAME(sys_socketpair)
> 
> 55 = 0x37 ....  I understand that....I don't see where GR20 is mapped to the
> the syscall number.... (Not really important that I know now... but curious)

A system call on PA-RISC Linux looks like this:

        be,l    0x100(%sr2,%r0),%sr0,%r31
        ldi     <syscall number>,%r20

(with six possible arguments in %r26 - %r21)

> From this statement, I assume it is a kernel problem and not a glibc
> problem ... since the kernel would perform the mapping?  I'll start digging
> around in the kernel and see what I can find.... any hints where to start?

I think the explanation regarding the TLB miss handlers is correct,
but I haven't tried on the C360 since it doesn't get to userland for
me :(

-- 
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.

  reply	other threads:[~2000-09-03  5:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-02 22:41 [parisc-linux] Boot error on C200+ Ryan Bradetich
2000-09-03  1:00 ` David Huggins-Daines
2000-09-03  2:26   ` Ryan Bradetich
2000-09-03  5:16     ` David Huggins-Daines [this message]
2000-09-03 16:57   ` bame
2000-09-03  2:07 ` Bob Pflederer
2000-09-03  2:29   ` Ryan Bradetich
  -- strict thread matches above, loose matches on Subject: below --
2000-09-03  3:29 John Marvin
2000-09-05 17:02 ` Bob Pflederer
2000-09-06  1:45   ` Ryan Bradetich

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=877l8ukqbl.fsf@linuxcare.com \
    --to=dhd@linuxcare.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=rbradetich@uswest.net \
    /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