public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Hien Nguyen <hien@us.ibm.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: 03-23-2006 Meeting minutes
Date: Thu, 23 Mar 2006 23:31:00 -0000	[thread overview]
Message-ID: <44232FE2.8080509@us.ibm.com> (raw)

Attendees
IBM – Ananth, Prasanna, Jim, Hien, Richard, Tom, Vara
Redhat – Will, Frank, Elena
Intel – Anil, Josh
Hitachi – Satoshi

Userspace probes -
Prasanna posted user space probes patch on LKML. Andrew wanted a details 
description of the design, and advantage/disadvantage of this approach.
Someone suggested to do everything from the user space via a system call 
(similar to ptrace).
Prasanna raised some questions that we need to have the answers for
- Considering for global probes vs local probes
- Should the handler run in the interrupt context?
- Can and should the handler run in the userspace?
(Prasanna please correct my notes )
Even with the system call interface we still be able to use lot of 
current code.
Sometime ago, Roland mentionned that he will improve ptrace interface, 
we probably should talk with Roland on kprobes ptrace marriage (did I 
get it right?), Will volunteer to check with Roland on that. However, 
Richard thinks it is a bad idea.
Prasanna will write up the requirement and the design and post on LKML 
again next week, let's discuss all issues on LKML.
Systemtap core team should be aware of the userspace probes discussion 
on LKML.

LKLM watch -
Hitachi will watch LKML next week.

elfutils - No new news

Systemtap GUI -
Hien will lead a team of three intern students to work on the systemtap 
gui. It is an open source project based on Eclipse. The project 
discussion will go on systemtap mailing list. IBM will introduce the 
SpeedTeam (interns) to the systemtap team when they arrive in April.

Face to face meeting -
Richard would like to meet everyone in his up comming trip to USA. Elena 
is willing to host in the following location
WestFord, MA
Toronto Canada
Mountain view, CA
somewhere? North Carolina
Intel and IBM could host the meeting too (Beaverton for IBM, Mountain 
view for Intel). For India folks to attend the meeting in May, Toronto 
is the best place (due to Visa issue)
Elena will finalize the plan with folks offline.

Redhat support for systems running systemtap -
Currently unverified kernel modules are not supported by Redhat. Elena 
will find out who can make that decision to change that for systemtap 
generated modules.

Xen support -
Elena indicated that Xen is now available on FC5, we should test 
systemtap on Xen (both DOM0 and DOMu).

RHEL4 U4 Back port -
Anil said there is some concerns at Redhat to get the back port patch 
into the RHEL4 U4 kernel. Elena will take care of that.

RHEL5 -
Userspace probes may not make RHEL5. Elena indicated that if the 
userspace patch could get into the mm tree that would be good.

Performance monitor tapset -
Will will rewrite the design base on the feed back he got and post again.
There were much discussion about starting and stopping counters. 
Discussion will continue on the mailing list.

Binary tracing -
Tom posted a proposed implimentation and a prototype on the bz#2046. 
Frank said the discussion should move to the systemtap mailing list.

Systemtap to allow raw access to relayfs channels -
There is a systemtap's customer wants to use systemtap to collect the 
data via relayfs without stpd draining the data. Jim will post a write 
up on this.

Exception Handling -
Anil indicated that currently if people do the usercopy in the kprobe 
handler (in the case of plain kprobe module) they will get the warning. 
Systemtap does not have that issue since it uses its own copyuser in the 
runtime.

Anil announced that the re-entry patch for x86_64 has been accepted.
Ananth - Kprobes Booster patch is on its way to Linus.








             reply	other threads:[~2006-03-23 23:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 23:31 Hien Nguyen [this message]
2006-03-24  0:38 Stone, Joshua I
2006-03-24  0:42 ` Roland McGrath
2006-03-24 14:35   ` William Cohen

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=44232FE2.8080509@us.ibm.com \
    --to=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).