[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Understanding Alpha syscalls
- From: Uncle George <gatgul voicenet com>
- To: axp-list redhat com, "B. James Phillippe" <bryan terran org>
- Subject: Re: Understanding Alpha syscalls
- Date: Wed, 02 Jun 1999 17:53:08 -0400
most of all the syscall interpretation is done in the assembler file entry.S
in arch/alpha/kernel. if u know ur syscall #, u can look it up at
sys_call_table: + offset(syscall #).
hope this helps.
gat
B. James Phillippe wrote:
> Greetings,
>
> I'm getting quite lost trying to map the sequence of events between a call
> to "open" on a device node from user-space to the invocation of the open
> method of a file_operations struct. Can anyone bail me out of this mess?
>
> The C library part is understandable (syscall macros, etc). I am sort of
> seeing how system calls are entered in the kernel on Alpha, but it's harder
> to follow than x86 because it looks like the PAL does some (a lot?) of the
> work. The part I am having the most trouble with is finding where kernel C
> code is re-entered to dispatch the file_operations methods..
>
> Some pointers or hints of where to look would be helpful. Also, I'm not
> sure what mechanism is used to signal the processor/kernel that a system
> call has been invoked; on x86 it's something like instruction "int $0x80".
>
> thanks,
> -bp
> --
> # Software Development, WatchGuard Inc.
> # Projects, PGP key at http://www.terran.org/~bryan
>
> --
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]