From: "Oestman, Fredrik" <Fredrik_Oestman@mentor.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Cc: "Oestman, Fredrik" <Fredrik_Oestman@mentor.com>
Subject:
Date: Fri, 23 Dec 2011 08:21:00 -0000 [thread overview]
Message-ID: <524C960C5DFC794E82BE548D825F05CF01D44E@EU-MBX-04.mgc.mentorg.com> (raw)
This is an attempt to make the .meta information for the example scripts correct and consistent. Correctness is defined by the rules in the README.
We hope this will help us present the example scripts better to the user in an Eclipse-based GUI environment.
Fredrik Östman (10):
Correct and consistent .meta files for example scripts: general
Correct and consistent .meta files for example scripts: interrupt
Correct and consistent .meta files for example scripts: io
Correct and consistent .meta files for example scripts: locks
Correct and consistent .meta files for example scripts: memory
Correct and consistent .meta files for example scripts: network
Correct and consistent .meta files for example scripts: process
Correct and consistent .meta files for example scripts: profiling
Correct and consistent .meta files for example scripts:
virtualization
Correct and consistent .meta files for example scripts: README
testsuite/systemtap.examples/README | 83 +++++++++++---------
.../systemtap.examples/general/ansi_colors.meta | 2 +-
.../systemtap.examples/general/ansi_colors2.meta | 2 +-
testsuite/systemtap.examples/general/badname.meta | 2 +-
.../systemtap.examples/general/eventcount.meta | 6 +-
.../general/func_time_stats.meta | 12 ++-
testsuite/systemtap.examples/general/graphs.meta | 4 +-
.../systemtap.examples/general/helloworld.meta | 2 +-
.../general/para-callgraph-verbose.meta | 10 ++-
.../systemtap.examples/general/para-callgraph.meta | 10 ++-
testsuite/systemtap.examples/general/sizeof.meta | 11 ++-
testsuite/systemtap.examples/general/varwatch.meta | 9 ++-
testsuite/systemtap.examples/general/watchdog.meta | 10 ++-
.../interrupt/interrupts-by-dev.meta | 2 +-
testsuite/systemtap.examples/interrupt/scf.meta | 4 +-
testsuite/systemtap.examples/io/deviceseeks.meta | 2 +-
testsuite/systemtap.examples/io/disktop.meta | 2 +-
testsuite/systemtap.examples/io/io_submit.meta | 2 +-
testsuite/systemtap.examples/io/ioblktime.meta | 2 +-
testsuite/systemtap.examples/io/iostat-scsi.meta | 2 +-
testsuite/systemtap.examples/io/iotime.meta | 4 +-
testsuite/systemtap.examples/io/iotop.meta | 2 +-
testsuite/systemtap.examples/io/mbrwatch.meta | 9 ++-
testsuite/systemtap.examples/io/traceio.meta | 2 +-
testsuite/systemtap.examples/io/traceio2.meta | 2 +-
testsuite/systemtap.examples/io/ttyspy.meta | 9 ++-
testsuite/systemtap.examples/locks/bkl.meta | 7 +-
testsuite/systemtap.examples/locks/bkl_stats.meta | 4 +-
.../systemtap.examples/memory/hw_watch_addr.meta | 2 +-
.../systemtap.examples/memory/hw_watch_sym.meta | 2 +-
.../systemtap.examples/memory/kmalloc-top.meta | 2 +-
.../systemtap.examples/memory/numa_faults.meta | 2 +-
.../systemtap.examples/memory/overcommit.meta | 11 ++-
.../systemtap.examples/memory/vm.tracepoints.meta | 4 +-
testsuite/systemtap.examples/network/autofs4.meta | 9 ++-
.../systemtap.examples/network/dropwatch.meta | 4 +-
.../systemtap.examples/network/nfsd_unlink.meta | 5 +-
.../network/sk_stream_wait_memory.meta | 4 +-
.../systemtap.examples/network/socket-trace.meta | 2 +-
.../network/tcp_connections.meta | 2 +-
.../systemtap.examples/network/tcp_init_cwnd.meta | 8 ++-
.../systemtap.examples/network/tcp_trace.meta | 6 +-
.../systemtap.examples/network/tcpipstat.meta | 6 +-
testsuite/systemtap.examples/process/chng_cpu.meta | 2 +-
.../systemtap.examples/process/cycle_thief.meta | 4 +-
testsuite/systemtap.examples/process/errsnoop.meta | 12 ++-
testsuite/systemtap.examples/process/migrate.meta | 2 +-
testsuite/systemtap.examples/process/noptrace.meta | 12 ++-
testsuite/systemtap.examples/process/pf2.meta | 6 +-
testsuite/systemtap.examples/process/pfiles.meta | 11 ++-
testsuite/systemtap.examples/process/plimit.meta | 10 ++-
.../systemtap.examples/process/schedtimes.meta | 2 +-
testsuite/systemtap.examples/process/sigkill.meta | 2 +-
testsuite/systemtap.examples/process/sigmon.meta | 4 +-
.../process/sleepingBeauties.meta | 8 ++-
.../systemtap.examples/process/sleeptime.meta | 4 +-
.../systemtap.examples/process/syscalltimes.meta | 2 +-
testsuite/systemtap.examples/profiling/errno.meta | 2 +-
.../systemtap.examples/profiling/fntimes.meta | 9 ++-
.../profiling/functioncallcount.meta | 6 +-
.../systemtap.examples/profiling/latencytap.meta | 4 +-
.../systemtap.examples/profiling/linetimes.meta | 4 +-
.../systemtap.examples/profiling/periodic.meta | 6 +-
.../systemtap.examples/profiling/sched_switch.meta | 7 +-
.../systemtap.examples/profiling/thread-times.meta | 9 ++-
.../systemtap.examples/profiling/timeout.meta | 2 +-
testsuite/systemtap.examples/profiling/topsys.meta | 2 +-
.../virtualization/kvm_service_time.meta | 2 +-
.../virtualization/qemu_count.meta | 2 +-
.../systemtap.examples/virtualization/qemu_io.meta | 2 +-
70 files changed, 276 insertions(+), 149 deletions(-)
--
1.7.6.4
reply other threads:[~2011-12-23 8:21 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=524C960C5DFC794E82BE548D825F05CF01D44E@EU-MBX-04.mgc.mentorg.com \
--to=fredrik_oestman@mentor.com \
--cc=systemtap@sourceware.org \
/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).