From: Steven Rostedt <rostedt@goodmis.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [topic proposal] tracepoints and ABI stability warranties
Date: Tue, 6 Sep 2016 15:22:43 -0400 [thread overview]
Message-ID: <20160906152243.766f3845@gandalf.local.home> (raw)
In-Reply-To: <20160906185143.GF2356@ZenIV.linux.org.uk>
On Tue, 6 Sep 2016 19:51:43 +0100
Al Viro <viro@ZenIV.linux.org.uk> wrote:
> I think this is something that needs to be discussed at KS; IMO we
> need at least some way to express the degree of stability promises made
> wrt individual tracepoints and some mechanisms for preventing silent creep
> towards full stability; something along the lines of "unstable tracepoint $FOO
> used by $PROGRAM, kernel tainted", at least.
What about having a set of tracepoints that are only enabled if one
adds to the kernel command line "this-kernel-is-broken" and a big
printk banner saying something like:
*****************************************************************
*****************************************************************
** WARNING WARNING WARNING WARNING WARNING WARNING **
** **
** This kernel is BROKEN! Do not use in production **
*****************************************************************
*****************************************************************
Then the tracepoints in vfs will appear.
This worked so far with my trace_printk() usage.
-- Steve
next prev parent reply other threads:[~2016-09-06 19:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:51 Al Viro
2016-09-06 19:22 ` Steven Rostedt [this message]
2016-09-06 21:36 ` Alexey Dobriyan
2016-09-06 21:53 ` Steven Rostedt
2016-09-06 22:41 ` Alexey Dobriyan
2016-09-06 23:12 ` Steven Rostedt
2016-09-08 11:43 ` Alexey Dobriyan
2016-09-07 5:10 ` Al Viro
2016-09-07 5:30 ` Andy Lutomirski
2016-09-07 6:41 ` Vlastimil Babka
2016-09-19 12:51 ` Michal Hocko
2016-09-07 13:15 ` Christian Borntraeger
2016-09-07 15:30 ` Shuah Khan
2016-09-07 16:10 ` Rik van Riel
2016-09-08 3:24 ` Masami Hiramatsu
2016-09-15 19:23 ` Mark Brown
2016-09-06 22:02 ` Alexey Dobriyan
2016-09-06 22:15 ` Steven Rostedt
2016-09-06 21:05 ` Shuah Khan
2016-09-08 3:13 ` Masami Hiramatsu
2016-09-07 23:17 ` Masami Hiramatsu
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=20160906152243.766f3845@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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