public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wenji dot huang at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/10703] compilation error of tracepoint on 2.6.32
Date: Tue, 29 Sep 2009 07:01:00 -0000	[thread overview]
Message-ID: <20090929070114.20704.qmail@sourceware.org> (raw)
In-Reply-To: <20090929065735.10703.wenji.huang@oracle.com>


------- Additional Comments From wenji dot huang at oracle dot com  2009-09-29 07:01 -------
This is introduced by

ext4: Add new tracepoint: trace_ext4_da_write_pages()
author	Theodore Ts'o <tytso@mit.edu>
	Tue, 1 Sep 2009 03:13:11 +0000 (23:13 -0400)
committer	Theodore Ts'o <tytso@mit.edu>
	Tue, 1 Sep 2009 03:13:11 +0000 (23:13 -0400)
commit	b3a3ca8ca0c3c29abc5b2bfe94bb14f3f4590df9
tree	1006f780d43ec8ff90ed11b1eb0d5ed961c9f613	tree | snapshot
parent	de89de6e0cf4b1eb13f27137cf2aa40d287aabdf	commit | diff
ext4: Add new tracepoint: trace_ext4_da_write_pages()

Add a new tracepoint which shows the pages that will be written using
write_cache_pages() by ext4_da_writepages().

Seems fs/ext4/ext4.h should be included into the generated C file,
but searching path is a problem since ext4.h isn't packaged up as a
part of a distribution kernel's header files.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=10703

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  reply	other threads:[~2009-09-29  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29  6:57 [Bug testsuite/10703] New: " wenji dot huang at oracle dot com
2009-09-29  7:01 ` wenji dot huang at oracle dot com [this message]
2009-09-29 12:13 ` [Bug testsuite/10703] compilation error of ext4 " fche at redhat dot com
2009-09-29 19:21 ` jistone at redhat dot com
2009-11-11  4:56 ` wenji dot huang at oracle dot com

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=20090929070114.20704.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).