All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Uladzislau Rezki <urezki@gmail.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>, RCU <rcu@vger.kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Axtens <dja@axtens.net>,
	Frederic Weisbecker <frederic@kernel.org>,
	Neeraj Upadhyay <neeraju@codeaurora.org>,
	Joel Fernandes <joel@joelfernandes.org>,
	Michal Hocko <mhocko@suse.com>,
	"Theodore Y . Ts'o" <tytso@mit.edu>,
	Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>
Subject: Re: [PATCH] kprobes: Fix to delay the kprobes jump optimization
Date: Fri, 19 Feb 2021 14:14:29 -0500	[thread overview]
Message-ID: <20210219141429.53def012@gandalf.local.home> (raw)
In-Reply-To: <20210219181811.GY2743@paulmck-ThinkPad-P72>

On Fri, 19 Feb 2021 10:18:11 -0800
"Paul E. McKenney" <paulmck@kernel.org> wrote:

> We can further prevent entry into dyntick-idle state until
> the ksoftirqd kthreads have been spawned, which means that if softirq
> handlers must be deferred, they will be resumed within one jiffy by the
> next scheduler-clock interrupt.

Why not just prevent entry into dyntick-idle state until the system is
finished booting? As you said; There should be no latency-sensitive
applications running, until after we started the system.

-- Steve

  parent reply	other threads:[~2021-02-19 19:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 14:29 [PATCH] kprobes: Fix to delay the kprobes jump optimization Masami Hiramatsu
2021-02-18 15:15 ` Paul E. McKenney
2021-02-19  8:17   ` Sebastian Andrzej Siewior
2021-02-19 10:49     ` Uladzislau Rezki
2021-02-19 10:57       ` Sebastian Andrzej Siewior
2021-02-19 11:13         ` Uladzislau Rezki
2021-02-19 11:17           ` Sebastian Andrzej Siewior
2021-02-19 11:23             ` Uladzislau Rezki
2021-02-19 11:27               ` Uladzislau Rezki
2021-02-19 18:18                 ` Paul E. McKenney
2021-02-19 18:33                   ` Paul E. McKenney
2021-02-19 19:34                     ` Paul E. McKenney
2021-02-19 20:02                     ` Steven Rostedt
2021-02-19 21:22                       ` Paul E. McKenney
2021-02-22 10:21                     ` Sebastian Andrzej Siewior
2021-02-22 12:54                       ` Uladzislau Rezki
2021-02-22 15:09                         ` Paul E. McKenney
2021-02-22 17:16                           ` Uladzislau Rezki
2021-02-22 18:16                             ` Paul E. McKenney
2021-02-22 19:07                               ` Uladzislau Rezki
2021-02-22 21:32                                 ` Paul E. McKenney
2021-02-19 19:14                   ` Steven Rostedt [this message]
2021-02-19 19:45                     ` Paul E. McKenney
2021-02-19 20:04                       ` Paul E. McKenney
2021-02-22 10:04                   ` Sebastian Andrzej Siewior
2021-02-19 19:36 ` Steven Rostedt
2021-02-19 19:47   ` Paul E. McKenney
2021-02-19 19:58     ` Steven Rostedt
2021-02-19 20:04       ` Paul E. McKenney
2021-02-22 12:06         ` 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=20210219141429.53def012@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=dja@axtens.net \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=neeraju@codeaurora.org \
    --cc=oleksiy.avramchenko@sonymobile.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tytso@mit.edu \
    --cc=urezki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.