From: Yuri Frolov <yfrolov@ru•mvista.com>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: Unsuccessfull system call interception. Please, help to correct it or make a suggestion.
Date: Mon, 28 Jun 2004 16:01:29 +0400 [thread overview]
Message-ID: <40E00899.2050906@ru.mvista.com> (raw)
In-Reply-To: <16604.50307.901331.251674@cargo.ozlabs.ibm.com>
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?
>
>Paul.
>
>
>
>
>
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/
next prev parent reply other threads:[~2004-06-28 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 12:11 Unsuccessfull system call interception. Please, help to correct it or make a suggestion Yuri Frolov
2004-06-26 0:34 ` Paul Mackerras
2004-06-28 12:01 ` Yuri Frolov [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-25 12:13 Yuri Frolov
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=40E00899.2050906@ru.mvista.com \
--to=yfrolov@ru$(echo .)mvista.com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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