From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Kacur <jkacur@redhat.com>
Cc: "Joakim Hernberg" <jhernberg@alchemy.lu>,
linux-rt-users@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin.
Date: Tue, 22 Dec 2015 17:34:23 +0100 [thread overview]
Message-ID: <56797B8F.6090008@linutronix.de> (raw)
In-Reply-To: <591364261.1447150.1450801543631.JavaMail.zimbra@redhat.com>
On 12/22/2015 05:25 PM, John Kacur wrote:
> The script can be made to handle it, that's not a big deal. I think the historical
> reason was worrying that people could be accidentally running a kernel with
> some really heavy weight debugging that would affect performance. However, let people
> hang themselves if they want.
How can people hang themselves if they build it *into* the kernel? If I
understand *how* this can happen I will try to address it. However from
what I can see right now, nothing will happen if this module is built
into the kernel.
>
> John
>
Sebastian
next prev parent reply other threads:[~2015-12-22 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 17:33 [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin Joakim Hernberg
2015-12-11 16:52 ` Sebastian Andrzej Siewior
2015-12-11 19:47 ` Joakim Hernberg
2015-12-13 10:39 ` Joakim Hernberg
2015-12-22 15:11 ` Sebastian Andrzej Siewior
2015-12-22 16:25 ` John Kacur
2015-12-22 16:34 ` Sebastian Andrzej Siewior [this message]
2015-12-22 16:43 ` John Kacur
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=56797B8F.6090008@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jhernberg@alchemy.lu \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).