From: "Frank Ch. Eigler" <fche@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: ltt-dev@shafik.org, Systemtap List <systemtap@sources.redhat.com>
Subject: Re: patches to actually use markers?
Date: Fri, 16 Nov 2007 20:27:00 -0000 [thread overview]
Message-ID: <20071116202645.GB25326@redhat.com> (raw)
In-Reply-To: <20071116201015.GA29545@Krystal>
Hi -
On Fri, Nov 16, 2007 at 03:10:15PM -0500, Mathieu Desnoyers wrote:
> [...]
> > How would this syscall specific function get ebx or the string,
> > without ebx (or regs) being passed as marker arguments?
> That's the idea : in the syscall specific function (not in
> syscall_trace()), we add another marker that takes the syscall
> specific arguments as parameter. I think we use the same approach
> there.
I see. Yes, per-systemcall markers would be welcome by our group, and
ones not dependent on TIF_TRACE or whatnot even more so. But were
trying not to get too optimistic.
> What I was saying is that we can't extract the string from
> syscall_trace() because we have no idea it is a string.
If "we" is a marker callback function that is given the system call
number, it can be taught. This is the sort of thing we do currently
in systemtap script code based upon kprobes.
- FChE
next prev parent reply other threads:[~2007-11-16 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 19:26 David Smith
2007-10-29 22:05 ` Mathieu Desnoyers
2007-10-31 16:29 ` David Smith
2007-10-31 16:58 ` Mathieu Desnoyers
2007-10-31 18:12 ` Mathieu Desnoyers
2007-11-01 3:34 ` Mathieu Desnoyers
2007-11-16 19:13 ` David Smith
2007-11-16 19:24 ` Mathieu Desnoyers
2007-11-16 19:56 ` Frank Ch. Eigler
2007-11-16 20:10 ` Mathieu Desnoyers
2007-11-16 20:27 ` Frank Ch. Eigler [this message]
2007-11-16 20:35 ` Mathieu Desnoyers
2007-11-16 20:43 ` Frank Ch. Eigler
2007-11-16 22:03 ` Mathieu Desnoyers
2007-11-16 22:35 ` Frank Ch. Eigler
2007-11-20 16:50 ` Mathieu Desnoyers
2007-11-20 15:22 ` David Smith
2007-11-20 16:22 ` [Ltt-dev] " Mathieu Desnoyers
2007-11-20 20:43 ` David Smith
2007-11-20 18:46 ` Mathieu Desnoyers
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=20071116202645.GB25326@redhat.com \
--to=fche@redhat.com \
--cc=ltt-dev@shafik.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=systemtap@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).