From: "argetek senvx" <argetek.senvx@gmail.com>
To: "Jim Keniston" <jkenisto@us.ibm.com>
Cc: systemtap@sourceware.org
Subject: Re: Workarounds for very useful developer userspace tracing scripts
Date: Sat, 09 Jun 2007 22:35:00 -0000 [thread overview]
Message-ID: <7d5f758c0706091535m5d69728blc6382ac91efa12ef@mail.gmail.com> (raw)
In-Reply-To: <1181420180.3781.29.camel@ibm-ni9dztukfq8.beaverton.ibm.com>
Thanks again, Jim.
> I can assure you that stap guys are listening.
>
Cool. With a great SystemTap interface over uprobes, sky is the limit!
> > 2.6.21-1.3194.fc7-x86_64$ patch -up1 --dry-run < ~/uprobes.patch
> >
>
> Was that the problem?
That's correct - Applied the "three" patches from May 25 (/26
UTC), also threw in your SMP multithreading race fix from today.
>
> These patches should apply cleanly to any utrace-enabled kernel, with
> the possible exceptions of the patches to the Makefiles and Kconfig
> file, which should be easy to hand-patch.
>
Indeed - Thanks again!
Compile's chugging away... :-)
Regards,
~ argetek
prev parent reply other threads:[~2007-06-09 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 17:07 argetek senvx
2007-06-08 20:15 ` Jim Keniston
2007-06-09 20:12 ` argetek senvx
2007-06-09 21:16 ` Jim Keniston
2007-06-09 22:35 ` argetek senvx [this message]
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=7d5f758c0706091535m5d69728blc6382ac91efa12ef@mail.gmail.com \
--to=argetek.senvx@gmail.com \
--cc=jkenisto@us.ibm.com \
--cc=systemtap@sourceware.org \
/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).