From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH 0/3] clear_warn_once: add timed interval resetting
Date: Mon, 30 Nov 2020 12:38:43 -0500 [thread overview]
Message-ID: <20201130173842.GB26693@windriver.com> (raw)
In-Reply-To: <20201130030828.GA1363814@tassilo.jf.intel.com>
[Re: [PATCH 0/3] clear_warn_once: add timed interval resetting] On 29/11/2020 (Sun 19:08) Andi Kleen wrote:
> On Thu, Nov 26, 2020 at 01:30:26AM -0500, Paul Gortmaker wrote:
> > But you currently can't make use of clear_warn_once unless you've got
> > debugfs enabled and mounted - which may not be desired by some people
> > in some deployment situations.
>
> Seems awfully special purpose. The problem with debugfs is security,
> or is it no convenient process that could do cron like functionality?
My understanding is that it is a bit of both. As users of rt tasks,
they won't be running anything like cron that could add to OS jitter on
the (presumably minimal) rootfs - so they were looking for a clean
engineered solution with near zero overhead, that they could easily
deploy on all nodes after the rt tuning was 99% completed and node
images had been bundled. Just to be sure everything was operating as
they'd aimed to achieve.
I thought a boot arg (and the internal timer) seemed like a good fit to
that requirement. No kernel or rootfs rebuilding required. And I
figured others might be in the same boat and could use it too.
Paul.
--
>
> If it's the first, perhaps what they really need is a way to get
> a partial debugfs?
>
> -Andi
next prev parent reply other threads:[~2020-11-30 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 6:30 [PATCH 0/3] clear_warn_once: add timed interval resetting Paul Gortmaker
2020-11-26 6:30 ` [PATCH 1/3] clear_warn_once: expand debugfs to include read support Paul Gortmaker
2020-11-26 6:30 ` [PATCH 2/3] clear_warn_once: bind a timer to written reset value Paul Gortmaker
2020-11-30 16:20 ` Steven Rostedt
2020-11-30 17:17 ` Paul Gortmaker
2020-12-01 3:36 ` Steven Rostedt
2020-11-26 6:30 ` [PATCH 3/3] clear_warn_once: add a warn_once_reset= boot parameter Paul Gortmaker
2020-11-27 16:13 ` [PATCH 0/3] clear_warn_once: add timed interval resetting Petr Mladek
2020-11-27 17:43 ` Paul Gortmaker
2020-12-01 12:59 ` Petr Mladek
2020-11-30 6:02 ` Sergey Senozhatsky
2020-11-30 16:24 ` Steven Rostedt
2020-11-30 3:08 ` Andi Kleen
2020-11-30 17:38 ` Paul Gortmaker [this message]
2020-12-01 12:49 ` Petr Mladek
2020-12-01 18:05 ` Paul Gortmaker
2020-12-09 16:37 ` Petr Mladek
2020-12-09 17:21 ` Paul Gortmaker
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=20201130173842.GB26693@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=ak@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.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