From: Mark Brown <broonie@kernel.org>
To: Rik van Riel <riel@redhat.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [Ksummit-discuss] [topic proposal] tracepoints and ABI stability warranties
Date: Thu, 15 Sep 2016 20:23:11 +0100 [thread overview]
Message-ID: <20160915192311.GS27974@sirena.org.uk> (raw)
In-Reply-To: <1473264649.10218.56.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
On Wed, Sep 07, 2016 at 12:10:49PM -0400, Rik van Riel wrote:
> From an enterprise distro (and user) point of view,
> it is important to be able to debug a kernel that
> is running on a production system (and developed
> some problem after a month of running), without
> having to reboot into a special "debug kernel".
>
> Being able to just fire up a tracer debugging
> script that can identify intermittent problems
> is an invaluable tool in making the kernel better
> for our users.
>
> Hamstringing our ability to make the kernel better,
> in order to keep the debugging ABI stable, is
> shooting ourselves (and our users) in the foot.
This also applies very much to embedded systems development. The
flight recorder aspect and the ability to turn on trace without
requiring a custom build be distributed and flashed are massively
helpful, I've seen people get really excited when they see tracepoints
for the first time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-15 19:23 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
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 [this message]
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=20160915192311.GS27974@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@kernel.org \
--cc=riel@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