From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Hien Nguyen <hien@us.ibm.com>
Cc: systemtap <systemtap@sources.redhat.com>
Subject: Re: 03-09-2006 meeting minutes
Date: Fri, 10 Mar 2006 10:01:00 -0000 [thread overview]
Message-ID: <20060310100040.GA7811@in.ibm.com> (raw)
In-Reply-To: <4410B5A7.8040303@us.ibm.com>
On Thu, Mar 09, 2006 at 03:09:27PM -0800, Hien Nguyen wrote:
> Attendees
...
> OLS paper -
> Thanks to Frank, the systemtap tutorial is fantastic. Prasanna indicates
> that some OLS papers are now in CVS (which CVS? Prasanna, please
> clarify) . Ananth mentioned that he wants to use Frank's tutorial in a
> conference in India (conference name?)
Systemtap CVS in private/ at the top level. And its not a conference - we
will be having some education sessions for members of our group here.
> Kprobes -
> Satoshi will port kprobes booster to x86_64 and ia64 but he/Hitachi does
> not have the expertise to port it to ppc64. Ananth will look in to this,
> but it is not a trivial task.
>
> Fault handling patch - Prasanna asked for help in testing the patch on
> ppc64. Hien will do that asap.
>
> Vara/Prasanna will update the kprobes todo list.
> Ananth indicated that user space probes is not ready for LKML, we need
> to resolve some issues, Richard had some ideas to address those issues.
> Ananth and Prasanna will discuss that off line with Richard.
>
> Ananth had problem compiling systemtap script on ppc64 (failed at stage
> 4). The problem could be the new systemcalls tapset. Hien will look into
> this problem.
Problem looks to be solved.. thanks Hien!
Ananth
prev parent reply other threads:[~2006-03-10 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 23:09 Hien Nguyen
2006-03-10 10:01 ` Ananth N Mavinakayanahalli [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=20060310100040.GA7811@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=hien@us.ibm.com \
--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).