From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
dzickus@redhat.com
Subject: Re: [PATCH 1/2] nohz: Disable LOCKUP_DETECTOR when NO_HZ_FULL is enabled
Date: Wed, 15 May 2013 10:37:29 +0200 [thread overview]
Message-ID: <20130515083729.GC10510@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <1368547372-21011-2-git-send-email-fweisbec@gmail.com>
On Tue, May 14, 2013 at 06:02:51PM +0200, Frederic Weisbecker wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> Trying to test the nohz_full code, I was not able to get it to work.
> Finally I enabled the tick_stop tracepoint and it showed:
>
> tick_stop: success=no msg=perf events running
>
> I talked to Frederic Weisbecker about this and he informed me that
> perf is used by the lockup detector. I checked the code, and sure
> enough it is.
>
> As perf is always running when LOCKUP_DETECTOR is enabled, which
> will always disable nohz_full from working, instead of confusing
> users, disable LOCKUP_DETECTOR when NO_HZ_FULL is enabled.
>
> When perf is changed such that it does not prevent nohz_full from
> working, then we can and should remove this constraint.
That's a bit contradictory in function, you want the NMI watchdog to
cover all code, so disabling whilst entering NO_HZ state is going to
make it not cover some code - *fail*.
Rather I would suggest disabling the NMI watchdog's runtime default; so
you can still enable it with something like:
echo 1 > /proc/sys/kernel/nmi_watchdog
next prev parent reply other threads:[~2013-05-15 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 16:02 [GIT PULL] Nohz fixes Frederic Weisbecker
2013-05-14 16:02 ` [PATCH 1/2] nohz: Disable LOCKUP_DETECTOR when NO_HZ_FULL is enabled Frederic Weisbecker
2013-05-15 8:37 ` Peter Zijlstra [this message]
2013-05-15 15:06 ` Don Zickus
2013-05-15 15:27 ` Steven Rostedt
2013-05-15 16:26 ` Don Zickus
2013-05-15 16:59 ` Peter Zijlstra
2013-05-15 17:04 ` Steven Rostedt
2013-05-16 8:10 ` Peter Zijlstra
2013-05-16 11:38 ` Frederic Weisbecker
2013-05-16 17:57 ` Peter Zijlstra
2013-05-16 15:07 ` Paul E. McKenney
2013-05-16 17:56 ` Peter Zijlstra
2013-05-16 18:32 ` Steven Rostedt
2013-05-16 23:14 ` Frederic Weisbecker
2013-05-19 16:18 ` Paul E. McKenney
2013-05-16 20:06 ` Paul E. McKenney
2013-05-15 17:11 ` Peter Zijlstra
2013-05-15 17:50 ` Don Zickus
2013-05-15 16:55 ` Peter Zijlstra
2013-05-15 15:59 ` Frederic Weisbecker
2013-05-14 16:02 ` [PATCH 2/2] nohz: Warn if the machine can not perform nohz_full Frederic Weisbecker
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=20130515083729.GC10510@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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