From: Al Viro <viro@ZenIV.linux.org.uk>
To: robert.foss@collabora.com
Cc: rostedt@goodmis.org, mingo@redhat.com, scott@ubuntu.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PACTH v1] trace: Add trace events for open(), exec() and uselib()
Date: Mon, 1 Aug 2016 19:10:14 +0100 [thread overview]
Message-ID: <20160801181014.GB2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1470072340-17748-1-git-send-email-robert.foss@collabora.com>
On Mon, Aug 01, 2016 at 01:25:40PM -0400, robert.foss@collabora.com wrote:
> From: Scott James Remnant <scott@ubuntu.com>
>
> This patch uses TRACE_EVENT to add tracepoints for the open(),
> exec() and uselib() syscalls so that ureadahead can cheaply trace
> the boot sequence to determine what to read to speed up the next.
NAK. No Tracepoints In VFS. Not going to happen - any tracepoint can all too
easily become a cast-in-stone userland ABI.
next prev parent reply other threads:[~2016-08-02 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 17:25 [PACTH v1] trace: Add trace events for open(), exec() and uselib() robert.foss
2016-08-01 17:44 ` Steven Rostedt
2016-08-01 18:13 ` Al Viro
2016-08-01 18:10 ` Al Viro [this message]
2016-08-01 19:51 ` Robert Foss
2016-08-01 20:31 ` Steven Rostedt
2016-08-02 8:11 ` Ingo Molnar
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=20160801181014.GB2356@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robert.foss@collabora.com \
--cc=rostedt@goodmis.org \
--cc=scott@ubuntu.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