From: Andy Gospodarek <gospo@redhat.com>
To: Andy Gospodarek <gospo@redhat.com>
Cc: Martin Hunt <hunt@redhat.com>, David Smith <dsmith@redhat.com>,
Mike Mason <mmlnx@us.ibm.com>,
systemtap@sources.redhat.com
Subject: Re: SystemTap on 2.6.23-rc8-mm2
Date: Thu, 04 Oct 2007 21:35:00 -0000 [thread overview]
Message-ID: <20071004213506.GB866@gospo.rdu.redhat.com> (raw)
In-Reply-To: <20071004211538.GA866@gospo.rdu.redhat.com>
On Thu, Oct 04, 2007 at 05:15:39PM -0400, Andy Gospodarek wrote:
> On Thu, Oct 04, 2007 at 05:10:51PM -0400, Martin Hunt wrote:
> > On Thu, 2007-10-04 at 16:29 -0400, Andy Gospodarek wrote:
> > > On Thu, Oct 04, 2007 at 03:07:00PM -0500, David Smith wrote:
> > > > David Smith wrote:
> > > > >Mike Mason wrote:
> > > > >>Just a heads up... I had to patch buildrun.cxx to get scripts to build
> > > > >>on 2.6.23-rc8-mm2 (CFLAGS changed to KBUILD_CFLAGS, CPPFLAGS changed
> > > > >>to KBUILD_CPPFLAGS). I've attached the patch below. I don't know
> > > > >>when or if this change will go into Linus' kernel. I'm also not sure
> > > > >>of the best way to ensure the correct CFLAGS are used in build_run.cxx
> > > > >>(maybe check s.kernel_release?).
> > > > >
> > > > >I've seen this also (and in fact I meant to check something in but got
> > > > >distracted by my other marker work). I believe my solution will be
> > > > >backwards compatible to 2.6.9 kernels - I've tested it on RHEL4 but I
> > > > >wanted to test f7 and RHEL5 to make sure I didn't break anything.
> > > >
> > > > I tested this on RHEL4, RHEL5, and f7. It seemed to work correctly
> > > > everywhere so I've checked my changes.
> > > >
> > >
> > > Interestingly I just pulled the latest sources and tried against Dave
> > > Miller's net-2.6.24 tree and I'm getting the following errors:
> > >
> > > WARNING: ignored message of type 5
> >
> > You're the second person today to remind me that warning is still in
> > there. I am working on a fix. It only happens when a module is loaded
> > when a systemtap script is running.
> >
> > Martin
> >
> >
>
> Aside from the warning it doesn't actually print my message, so the
> probe isn't too helpful. ;-)
OK, nevermind. I was looking at the wrong driver -- when I used one
that actually calls the function I'm probing it works. Sorry for the
noise....
next prev parent reply other threads:[~2007-10-04 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 16:21 Mike Mason
2007-10-04 18:34 ` David Smith
2007-10-04 20:07 ` David Smith
2007-10-04 20:29 ` Andy Gospodarek
2007-10-04 21:11 ` Martin Hunt
2007-10-04 21:15 ` Andy Gospodarek
2007-10-04 21:35 ` Andy Gospodarek [this message]
2007-10-04 21:22 ` Mike Mason
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=20071004213506.GB866@gospo.rdu.redhat.com \
--to=gospo@redhat.com \
--cc=dsmith@redhat.com \
--cc=hunt@redhat.com \
--cc=mmlnx@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).