From: Dave Jones <davej@codemonkey.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Self nomination
Date: Fri, 31 Jul 2015 14:17:58 -0400 [thread overview]
Message-ID: <20150731181757.GA8747@codemonkey.org.uk> (raw)
In-Reply-To: <20150731181245.GA5969@kroah.com>
On Fri, Jul 31, 2015 at 11:12:45AM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 31, 2015 at 12:51:53PM -0500, Bjorn Helgaas wrote:
> > I prefer that a dmesg collected in the simplest possible way, with no
> > special config or boot flags, be as useful as possible. So converting
> > to dynamic debug requires much more thought about which messages
> > should be always printed and which should become dynamic.
>
> Why would a debugging message ever not be dynamic? They are there for
> you to use, and turn off when you are done. If you want a user to
> report the output of them, then of course they should be dynamic so they
> can just write a line to a debugfs file and then start seeing them
This implies a user knows ahead of time what bugs they are going to hit,
and which messages they need to enable. For hard-to-reproduce bugs,
or bugs that exhibit non-obvious symptoms, this isn't workable.
Dave
next prev parent reply other threads:[~2015-07-31 18:55 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 2:55 Sasha Levin
2015-07-31 16:27 ` Bjorn Helgaas
2015-07-31 16:59 ` Guenter Roeck
2015-07-31 17:03 ` Bjorn Helgaas
2015-07-31 17:08 ` Greg KH
2015-07-31 17:15 ` Guenter Roeck
2015-07-31 17:51 ` Bjorn Helgaas
2015-07-31 18:12 ` Greg KH
2015-07-31 18:17 ` Dave Jones [this message]
2015-07-31 18:22 ` Greg KH
2015-07-31 18:59 ` Dan Williams
2015-08-01 13:03 ` Jiri Kosina
2015-07-31 17:26 ` James Bottomley
2015-07-31 17:43 ` Greg KH
2015-07-31 17:49 ` Sasha Levin
[not found] ` <alpine.DEB.2.02.1507310650220.2218@localhost6.localdomain6>
2015-07-31 17:49 ` Sasha Levin
2015-08-01 13:45 ` Dan Carpenter
2015-08-01 15:26 ` Sasha Levin
2015-08-01 16:22 ` Greg KH
2015-08-03 5:14 ` Sasha Levin
2015-08-01 20:30 ` Dave Jones
2015-08-03 5:17 ` Sasha Levin
2015-07-31 9:15 David Howells
2015-08-11 5:05 Haggai Eran
2015-08-24 4:20 [Ksummit-discuss] [TECH TOPIC] Kernel Hardening James Morris
2015-08-24 11:46 ` Jiri Kosina
2015-08-24 11:56 ` James Morris
2015-08-24 17:17 ` Kees Cook
2015-08-26 20:51 ` Kees Cook
2015-08-26 21:10 ` Matthew Garrett
2015-08-30 0:41 ` [Ksummit-discuss] Self nomination Matthew Garrett
2016-07-25 17:11 Johannes Weiner
2016-07-25 18:15 ` Rik van Riel
2016-07-26 10:56 ` Jan Kara
2016-07-26 13:10 ` Vlastimil Babka
2016-07-25 21:46 [Ksummit-discuss] self nomination Kevin Hilman
2016-07-26 15:44 [Ksummit-discuss] Self nomination David Woodhouse
2016-07-26 22:30 Dmitry Torokhov
2016-07-28 10:14 ` Marc Zyngier
2016-08-02 8:09 ` Linus Walleij
2016-08-02 23:00 ` Rafael J. Wysocki
2016-08-03 8:12 ` Marek Szyprowski
2016-08-06 0:20 ` Rafael J. Wysocki
2016-08-24 12:12 ` Marek Szyprowski
2016-08-24 17:32 ` Rafael J. Wysocki
2016-08-08 11:07 ` Lorenzo Pieralisi
2016-09-23 10:42 ` Grant Likely
2016-07-26 23:59 Stephen Rothwell
2016-07-28 12:23 ` Luis de Bethencourt
2016-07-27 0:50 Sergey Senozhatsky
2016-07-27 4:46 Darren Hart
2016-07-27 9:25 ` Linus Walleij
2016-07-27 17:02 ` Darren Hart
2016-08-04 12:30 ` Geert Uytterhoeven
2016-07-27 13:57 Lorenzo Pieralisi
2016-07-27 14:54 Mark Rutland
2016-07-27 23:20 [Ksummit-discuss] self nomination Davidlohr Bueso
2016-07-28 7:18 ` Jan Kara
2016-07-28 14:37 ` Rik van Riel
2016-07-29 6:17 ` Wangnan (F)
2016-07-29 23:53 ` Davidlohr Bueso
2016-07-28 17:29 James Bottomley
2016-07-28 17:31 ` James Bottomley
2016-07-29 15:13 [Ksummit-discuss] Self nomination Bartlomiej Zolnierkiewicz
2016-07-29 22:45 [Ksummit-discuss] self nomination Mimi Zohar
2016-07-30 0:32 [Ksummit-discuss] Self nomination Ben Hutchings
2016-07-31 6:57 Olof Johansson
2016-08-02 19:56 ` Mark Brown
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=20150731181757.GA8747@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=sasha.levin@oracle.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