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-02-2006 meeting minutes
Date: Sat, 04 Mar 2006 17:09:00 -0000	[thread overview]
Message-ID: <4409C9D6.608@us.ibm.com> (raw)

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

LKML watch -
Masami san posted a notes on the list. IBM next.

kprobes regression tests -
Everyone should check in the tests

RHEL4 U4 Backport -
Anil attached  a  patch  in the new  bz #2408.
Fault handling is broken, Prasanna has a patch ready to fix that. THis 
patch should go in the RHEL4 U4 if possible.
Ananth said that we have some slots in the spec file, so we must 
consider to consolidate those patches.
We need to test the back port patch on ppc64 and i386 (Josh)

Static validator -
Posted and checked in CVS. It checks modules for legal external 
references, and parses the disassembly for legal opcodes.

Probes fault handling -
Prasanna said that there are some issues in the case of multi-handler 
(keeping track of which one is faulted). Prasanna is working on a patch 
to address that.
In 2.6.16-rc4-mm2, we could register notify (when the frist probe 
inserted) and unregister notify (when the last probes removed)
Some discussions regarding how systemtap would use the fault handling.

Bugs -
bz#2046 - Tom sent Martin a patch to take care the new relayfs impact on 
the rumtime.
bz#2294 - Verified.  Fixed in 2.6.16-rc5
bz#2185 - Anil is working on this problem.  


                 reply	other threads:[~2006-03-04 17:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4409C9D6.608@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).