From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Joakim Hernberg <jhernberg@alchemy.lu>
Cc: 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>,
"John Kacur" <jkacur@redhat.com>
Subject: Re: [PATCH] make HWLAT_DETECTOR kernel config either disabled or a module, never builtin.
Date: Tue, 22 Dec 2015 16:11:17 +0100 [thread overview]
Message-ID: <20151222151117.GD27274@linutronix.de> (raw)
In-Reply-To: <20151213113935.59cfd847@balder.valhalla.alchemy.lu>
* Joakim Hernberg | 2015-12-13 11:39:35 [+0100]:
>I looked at the IRC logs from when this was discussed. The hwlatdetect
>script looks for the kernel module and will fail if it's built-in (or
>compressed). Also this quote from irc: <jkacur> I need to look
>at the code, but offhand, I think we said, it cannot be a built-in by design
Why can't it work by design in built-in mode? The module parameters
`enabled` and `threshold` can be set via debugfs (and via command line).
So I don't see here the difference between module and built-in.
Is there something I missed?
If the hwlatdetect script is not able to handle that then it deserves to
be fixed. The same goes for support of compressed modules.
>These were the reasons for the patch.
Sebastian
next prev parent reply other threads:[~2015-12-22 15:11 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 [this message]
2015-12-22 16:25 ` John Kacur
2015-12-22 16:34 ` Sebastian Andrzej Siewior
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=20151222151117.GD27274@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).