From: leitao@linux.vnet.ibm.com
To: systemtap@sources.redhat.com
Subject: [PATCH] A new testcase for tty tapset
Date: Tue, 20 Oct 2009 18:10:00 -0000 [thread overview]
Message-ID: <1256062127-13868-2-git-send-email-leitao@linux.vnet.ibm.com> (raw)
In-Reply-To: <1256062127-13868-1-git-send-email-leitao@linux.vnet.ibm.com>
This is a basic test to assure that the tty tapset is working
compiling and working properly
---
testsuite/buildok/tty.stp | 51 +++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 51 insertions(+), 0 deletions(-)
create mode 100755 testsuite/buildok/tty.stp
diff --git a/testsuite/buildok/tty.stp b/testsuite/buildok/tty.stp
new file mode 100755
index 0000000..0b5018d
--- /dev/null
+++ b/testsuite/buildok/tty.stp
@@ -0,0 +1,51 @@
+#! stap -wp4
+
+probe tty.poll{
+ printf("Pooling tty %s for wait queue key %d\n", file_name, wait_key);
+}
+
+probe tty.register {
+ printf("Device registered using index %d using driver %s(%s/%s)\n", index, driver_name, name, module)
+}
+
+probe tty.unregister {
+ printf("Device registered using index %d using driver %s(%s/%s)\n", index, driver_name, name, module)
+}
+
+probe tty.release {
+ printf("Closing file %s\n", file_name)
+ printf("INODE: number %d\nState: %d\nFlag: %d\n", inode_number, inode_state, inode_flags)
+ printf("File: %s (mode %x flags %x)\n", file_name, file_mode, file_flags)
+}
+
+probe tty.open {
+ printf("Opening tty file %s\n", file_name)
+ printf("INODE: number %d\nState: %d\nFlag: %d\n", inode_number, inode_state, inode_flags)
+ printf("File: %s mode %x flags %x\n", file_name, file_mode, file_flags)
+}
+
+probe tty.resize {
+ printf("Resizing %s from %dx%d (%d/%d) to %dx%d (%d/%d)\n", name, old_row, old_col, old_xpixel, old_ypixel,
+ new_row, new_col, new_xpixel, new_ypixel)
+}
+
+probe tty.ioctl {
+ printf("Ioctling file %s with %d %d\n", name, cmd, arg)
+}
+
+probe tty.init {
+ printf("new tty with name %s from driver %s and module %s\nn", driver_name, name, module)
+}
+
+probe tty.receive {
+ printf("Driver %s/%s (%d/%d) received %s (%s) with len %d\n", name, driver_name, index, id, cp, fp, count)
+}
+
+
+probe tty.write {
+ printf("Buffer %s (len %d) wrote on file %s (driver %s)\n", buffer, nr, file_name, driver_name)
+}
+
+probe tty.read {
+ printf("Reading tty file %s (driver %s) to a buffer with size %d containing %s\n", file_name, driver_name, nr, buffer)
+}
--
1.6.0.2
next prev parent reply other threads:[~2009-10-20 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 18:10 [PATCH] A new tapset that adds support for tty and serial devices leitao
2009-10-20 18:10 ` leitao [this message]
2009-10-20 18:10 ` [PATCH] tty: improving the ttyspy example leitao
2009-10-20 18:10 ` [PATCH] tty: Adding tty.stp to the documentation leitao
2009-10-20 21:23 ` Josh Stone
2009-10-20 21:07 ` [PATCH] tty: improving the ttyspy example David Smith
2009-10-21 13:34 ` Breno Leitao
2009-10-21 13:46 ` David Smith
2009-10-21 14:03 ` Breno Leitao
-- strict thread matches above, loose matches on Subject: below --
2009-10-02 21:03 [PATCH] A new tapset that adds support for tty and serial devices leitao
2009-10-02 21:03 ` [PATCH] A new testcase for tty tapset leitao
2009-10-13 20:55 ` David Smith
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=1256062127-13868-2-git-send-email-leitao@linux.vnet.ibm.com \
--to=leitao@linux.vnet.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).