From: "Oestman, Fredrik" <Fredrik_Oestman@mentor.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Cc: "Oestman, Fredrik" <Fredrik_Oestman@mentor.com>
Subject: [PATCH 05/10] Correct and consistent .meta files for example
Date: Fri, 23 Dec 2011 08:30:00 -0000 [thread overview]
Message-ID: <524C960C5DFC794E82BE548D825F05CF01D4C5@EU-MBX-04.mgc.mentorg.com> (raw)
Signed-off-by: Fredrik Östman <fredrik_oestman@mentor.com>
---
.../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 ++--
6 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/testsuite/systemtap.examples/memory/hw_watch_addr.meta b/testsuite/systemtap.examples/memory/hw_watch_addr.meta
index 6d640ce..c5ed34f 100644
--- a/testsuite/systemtap.examples/memory/hw_watch_addr.meta
+++ b/testsuite/systemtap.examples/memory/hw_watch_addr.meta
@@ -1,4 +1,4 @@
-title: Watch access to a kernel address using breakpoint hardware
+title: Watch a Kernel Address Using Breakpoint Hardware
name: hw_watch_addr.stp
version: 1.0
author: William Cohen
diff --git a/testsuite/systemtap.examples/memory/hw_watch_sym.meta b/testsuite/systemtap.examples/memory/hw_watch_sym.meta
index 0a7ce61..ffcf8b3 100644
--- a/testsuite/systemtap.examples/memory/hw_watch_sym.meta
+++ b/testsuite/systemtap.examples/memory/hw_watch_sym.meta
@@ -1,4 +1,4 @@
-title: Watch to a kernel symbol using breakpoint hardware
+title: Watch a Kernel Symbol Using Breakpoint Hardware
name: hw_watch_sym.stp
version: 1.0
author: William Cohen
diff --git a/testsuite/systemtap.examples/memory/kmalloc-top.meta b/testsuite/systemtap.examples/memory/kmalloc-top.meta
index 6388c3e..e7bd9de 100644
--- a/testsuite/systemtap.examples/memory/kmalloc-top.meta
+++ b/testsuite/systemtap.examples/memory/kmalloc-top.meta
@@ -1,4 +1,4 @@
-title: Show Paths to Kernel Malloc (kmalloc) Invocations
+title: Show Paths to Kernel Malloc Invocations
name: kmalloc-top
version: 1.0
author: anonymous
diff --git a/testsuite/systemtap.examples/memory/numa_faults.meta b/testsuite/systemtap.examples/memory/numa_faults.meta
index afd95e0..9d8b456 100644
--- a/testsuite/systemtap.examples/memory/numa_faults.meta
+++ b/testsuite/systemtap.examples/memory/numa_faults.meta
@@ -6,7 +6,7 @@ keywords: memory numa
subsystem: memory
status: production
exit: user-controlled
-output: list
+output: sorted-list
scope: system-wide
description: The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.
test_check: stap -p4 numa_faults.stp
diff --git a/testsuite/systemtap.examples/memory/overcommit.meta b/testsuite/systemtap.examples/memory/overcommit.meta
index 72fb157..5f4311d 100644
--- a/testsuite/systemtap.examples/memory/overcommit.meta
+++ b/testsuite/systemtap.examples/memory/overcommit.meta
@@ -1,6 +1,13 @@
-title: Log failed process memory allocation due to overcommit limits
+title: Log Failed Process Memory Allocation Due to Overcommit Limits
name: overcommit.stp
-keywords: memory process
+version: 1.0
+author: anonymous
+keywords: memory limits
+subsystem: memory
+status: proposed
+exit: user-controlled
+output: trace
+scope: system-wide
description: The overcommit.stp script prints a line each time the kernel refuses a memory allocation request from a process because of /proc/sys/vm/overcommit* limits.
test_check: stap -p4 overcommit.stp
test_installcheck: stap overcommit.stp -c "sleep 0.2"
diff --git a/testsuite/systemtap.examples/memory/vm.tracepoints.meta b/testsuite/systemtap.examples/memory/vm.tracepoints.meta
index 9fdb73f..c858d1b 100644
--- a/testsuite/systemtap.examples/memory/vm.tracepoints.meta
+++ b/testsuite/systemtap.examples/memory/vm.tracepoints.meta
@@ -1,8 +1,8 @@
-title: Collect slab allocation statistics
+title: Collect Slab Allocation Statistics
name: vm.tracepoints.stp
version: 1.0
author: Rajasekhar
-keywords: memory slab allocator
+keywords: memory slab statistics
subsystem: memory
status: production
exit: user-controlled
--
1.7.6.4
reply other threads:[~2011-12-23 8:28 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=524C960C5DFC794E82BE548D825F05CF01D4C5@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).