Unsuccessfull system call interception. Please, help to correct it or make a suggestion.
yfrolov at ru.mvista.com
Mon Jun 28 22:01:29 EST 2004
Paul Mackerras wrote:
>Yuri Frolov writes:
>>The problem: due to the necessity of logging system calls entry/exit
>>events by LTT the arch/ppc/kernel/entry.S was modified in this way:
>First, you don't say whether you are working on 2.4 or 2.6.
>Secondly, why can't you use the existing syscall trace infrastructure?
I'm working on linux-2.6.
I can't use the existing syscall trace infrastructure due to the
necessity to get LTT syscall interception mechanism working (LTT has
specific routines and binary format it uses to save info about syscall
entry/exit, I can't just get rid of it).
I would be happy to address this problem someone who subscribed to the
LTT mailing list, but seems the development of LTT tends to be more x86
centric. I posted the message because my strong opinion that the problem
is in the interaction between common ppc syscall handling mechanism and
the LTT portion which both written on pure ppc assembly...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev