public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Nguyen, Thang P" <thang.p.nguyen@intel.com>
To: "Badari Pulavarty" <pbadari@gmail.com>
Cc: "Mike Mason" <mmlnx@us.ibm.com>,
		"Vara Prasad" <prasadav@us.ibm.com>,
		"William Cohen" <wcohen@redhat.com>,
		"SystemTAP" <systemtap@sources.redhat.com>
Subject: RE: Anyone tried SystemTap with the latest RHEL5 Beta refresh
Date: Fri, 27 Oct 2006 21:05:00 -0000	[thread overview]
Message-ID: <9AE298E00BCF7B469C04BE82FCE78B8701CB7F36@scsmsx414.amr.corp.intel.com> (raw)

Can you check your tapset/ioblock.stp to see if you have this probe
ioblock.request() ?

If you don't, and you have ioblock.submit() instead, it means you have
an earlier version of tapset. In that case, you can try this modified
script.

#! stap

probe begin {
   printf("DEVNAME\tSECTOR\tRW\n")
}

probe ioblock.submit {
   printf("%s\t%d\t%d\n", devname, sector, rw)
}

probe ioblock.end {
    printf("%s\t%d\t%d\n", devname, sector, rw)
}


Thang


>-----Original Message-----
>From: Badari Pulavarty [mailto:pbadari@gmail.com]
>Sent: Friday, October 27, 2006 1:25 PM
>To: Nguyen, Thang P
>Cc: Mike Mason; Vara Prasad; William Cohen; SystemTAP
>Subject: RE: Anyone tried SystemTap with the latest RHEL5 Beta refresh
>
>On Thu, 2006-10-26 at 13:43 -0700, Nguyen, Thang P wrote:
>> For example:
>>
>> > stap ioblock_script.stp
>>
>> ------ ioblock_script.stp ----
>> #! stap
>>
>> probe begin {
>>   printf("DEVNAME\tSECTOR\tRW\n")
>> }
>> probe ioblock.request {
>>    printf("%s\t%d\t%s\n", devname, sector, bio_rw_str(rw))
>> }
>> probe ioblock.end {
>>    printf("%s\t%d\t%s\n", devname, sector, bio_rw_str(rw))
>> }
>>
>> Thang
>
>Okay, I just tried it on my x86_64 RHEL5 Beta machine
>(2.6.18-1.2714.el5) ..
>
># stap iostp.stp
>semantic error: probe point mismatch at position 1 (alternatives: end
>submit)
>while: resolving probe point ioblock.request
>semantic error: libdwfl failure (dwfl_linux_kernel_report_kernel): No
>such file or directory
>Ensure kernel debuginfo is installed
>while: resolving probe point kernel.function("bio_endio")
>semantic error: no match for probe point
>while: resolving probe point ioblock.end
>Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
>
>Thanks,
>Badari

             reply	other threads:[~2006-10-27 21:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 21:05 Nguyen, Thang P [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-01 18:51 Stone, Joshua I
2006-10-26 20:43 Nguyen, Thang P
2006-10-27  0:39 ` Li Guanglei
2006-10-27 20:25 ` Badari Pulavarty
2006-10-27 21:48   ` Frank Ch. Eigler
2006-10-30 18:28     ` Vara Prasad
2006-10-30 18:33       ` Frank Ch. Eigler
2006-10-31 23:15         ` Vara Prasad
2006-11-01  1:37           ` Tim Bird
2006-11-01  2:13           ` Frank Ch. Eigler
2006-11-01  6:51             ` Gerrit Huizenga
2006-11-01  8:56             ` Ken Robson
2006-11-01 12:40               ` Frank Ch. Eigler
2006-11-01 17:20                 ` David Wilder
2006-11-01 18:06                   ` David Smith
2006-11-01 18:12                     ` David Wilder
2006-11-01 18:23                       ` Frank Ch. Eigler
2006-11-01 18:27                         ` David Wilder
2006-11-01 19:31                           ` Frank Ch. Eigler
2006-11-01 19:07                       ` David Smith
2006-11-01 19:09                         ` David Wilder
2006-11-01 19:54                         ` Vara Prasad
2006-11-01 20:39                     ` Michael K. Dolan Jr.
2006-11-01 20:40                     ` Michael K. Dolan Jr.
2006-11-01 20:04             ` Vara Prasad
2006-11-01 21:11               ` Keshavamurthy, Anil S
2006-11-01 21:36                 ` Badari Pulavarty
2006-11-01 23:47           ` William Cohen
2006-11-02 19:09             ` Badari Pulavarty
2006-11-02 19:18               ` Frank Ch. Eigler
2006-11-02 23:53                 ` David Boreham
2006-11-02 23:55                 ` Badari Pulavarty
2006-11-03  0:35                   ` David Boreham
2006-11-03  2:22                   ` Frank Ch. Eigler
2006-10-26 18:28 Vara Prasad
2006-10-26 20:39 ` Mike Mason
2006-10-26 22:09 ` Frank Ch. Eigler

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=9AE298E00BCF7B469C04BE82FCE78B8701CB7F36@scsmsx414.amr.corp.intel.com \
    --to=thang.p.nguyen@intel.com \
    --cc=mmlnx@us.ibm.com \
    --cc=pbadari@gmail.com \
    --cc=prasadav@us.ibm.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@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).