Re: [PACTH v1] trace: Add trace events for open(), exec() and
uselib()
[Posted August 3, 2016 by corbet]
| From: |
| Ingo Molnar <mingo-AT-kernel.org> |
| To: |
| Al Viro <viro-AT-ZenIV.linux.org.uk> |
| Subject: |
| Re: [PACTH v1] trace: Add trace events for open(), exec() and uselib() |
| Date: |
| Tue, 2 Aug 2016 10:11:46 +0200 |
| Message-ID: |
| <20160802081146.GA9601@gmail.com> |
| Cc: |
| robert.foss-AT-collabora.com, rostedt-AT-goodmis.org, mingo-AT-redhat.com, scott-AT-ubuntu.com, linux-kernel-AT-vger.kernel.org, linux-fsdevel-AT-vger.kernel.org |
| Archive‑link: | |
Article |
* Al Viro <viro@ZenIV.linux.org.uk> wrote:
> 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.
And what's the problem with that? ABIs increase the utility of the kernel.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
