This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Duplicate events for 32-bit compatible syscall probes
- From: David Smith <dsmith at redhat dot com>
- To: Aryeh Weinreb <weinrea at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Fri, 26 Apr 2013 09:45:44 -0500
- Subject: Re: Duplicate events for 32-bit compatible syscall probes
- References: <CAE5ibEkN66WM4a1YD8r3xAqBb519iJNOThL3ek5otXcBJSaJwA at mail dot gmail dot com> <51792BCC dot 5090406 at redhat dot com> <51792D24 dot 5060002 at redhat dot com> <5179403A dot 6090204 at redhat dot com> <CAE5ibE=Gc6x+NGuB5yH8wN8LvOU=0wE-AkMWNHi7oUuO3Ayb+g at mail dot gmail dot com>
On 04/26/2013 08:41 AM, Aryeh Weinreb wrote:
>> OK, here's a solution that I actually tested with syscall.open.
>> Basically if the function name we're probing has 'compat_' in it, skip it.
>>
>> ====
>> probe syscall.open
>> {
>> if (isinstr(ppfunc(), "compat_")) {
>> next
>> }
>> # ... your real code here
>
> Thanks.
>
> Unfortunately I don't have ppfunc since I'm only on 1.8, but I guess
> if we are ignoring EFAULT I could also just:
> probe kernel.function("sys_mq_*)
>
ppfunc() is just a cut down pp() (with just the function part of the
probe point name). You should be able to use pp() instead of ppfunc().
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)