From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] x86/alternatives: Add cond_resched() to text_poke_bp_batch()
Date: Tue, 30 May 2023 08:35:53 -0400 [thread overview]
Message-ID: <20230530083553.6322240f@rorschach.local.home> (raw)
In-Reply-To: <20230530120148.GD156198@hirez.programming.kicks-ass.net>
On Tue, 30 May 2023 14:01:48 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Sun, May 28, 2023 at 08:46:52AM -0400, Steven Rostedt wrote:
> > diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
> > index f615e0cb6d93..e024eddd457f 100644
> > --- a/arch/x86/kernel/alternative.c
> > +++ b/arch/x86/kernel/alternative.c
> > @@ -1953,6 +1953,14 @@ static void text_poke_bp_batch(struct text_poke_loc *tp, unsigned int nr_entries
> > */
> > atomic_set_release(&bp_desc.refs, 1);
> >
> > + /*
> > + * Function tracing can enable thousands of places that need to be
> > + * updated. This can take quite some time, and with full kernel debugging
> > + * enabled, this could cause the softlockup watchdog to trigger.
> > + * Add cond_resched() calls to each phase.
> > + */
> > + cond_resched();
>
> But but but... you can only have TP_VEC_MAX pokes queued, which is 256
> on normal setups.
>
> Please explain how this leads to problems and why you need _3_
> reschedule points here.
Maybe this was me being overly paranoid (and thinking, it doesn't hurt).
I could try it with just adding one (to make sure it happens every
flush), and see if it doesn't trigger the softlock up.
-- Steve
next prev parent reply other threads:[~2023-05-30 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 12:46 [PATCH] x86/alternatives: Add cond_resched() to text_poke_bp_batch() Steven Rostedt
2023-05-29 2:52 ` Masami Hiramatsu
2023-05-29 3:21 ` Steven Rostedt
2023-05-30 12:01 ` Peter Zijlstra
2023-05-30 12:35 ` Steven Rostedt [this message]
2023-05-31 9:08 ` Steven Rostedt
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=20230530083553.6322240f@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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