From: Don Zickus <dzickus@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Tejun Heo <tj@kernel.org>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, Joshua Hunt <johunt@akamai.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] kernel/watchdog.c: Only output hw-PMU message once
Date: Mon, 21 Nov 2016 12:48:58 -0500 [thread overview]
Message-ID: <20161121174858.GB35881@redhat.com> (raw)
In-Reply-To: <1479746119-25239-1-git-send-email-prarit@redhat.com>
On Mon, Nov 21, 2016 at 11:35:19AM -0500, Prarit Bhargava wrote:
> When CONFIG_BOOTPARAM_HOTPLUG_CPU0 is enabled, the socket containing the
> boot cpu can be replaced. During the hot add event, the message
>
> NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
>
> is output implying that the NMI was disabled at some point. This is not the
> case and the message has caused confusion for users of systems that support
> socket removal.
>
> This patch modifies the message so that it only outputs a single time
> during runtime.
Hmm, it occurred to me, with pr_info_once, what happens if you disable and
re-enable, is this still printed?
echo 0 > /proc/sys/kernel/watchdog
echo 1 > /proc/sys/kernel/watchdog
Cheers,
Don
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Don Zickus <dzickus@redhat.com>
> Cc: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Joshua Hunt <johunt@akamai.com>
> Cc: Ingo Molnar <mingo@kernel.org>
> ---
> kernel/watchdog.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> index 9acb29f280ec..560414692c01 100644
> --- a/kernel/watchdog.c
> +++ b/kernel/watchdog.c
> @@ -615,7 +615,7 @@ static int watchdog_nmi_enable(unsigned int cpu)
> if (!IS_ERR(event)) {
> /* only print for cpu0 or different than cpu0 */
> if (cpu == 0 || cpu0_err)
> - pr_info("enabled on all CPUs, permanently consumes one hw-PMU counter.\n");
> + pr_info_once("enabled on all CPUs, permanently consumes one hw-PMU counter.\n");
> goto out_save;
> }
>
> --
> 1.7.9.3
>
next prev parent reply other threads:[~2016-11-21 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:35 Prarit Bhargava
2016-11-21 17:48 ` Don Zickus [this message]
2016-11-21 17:59 ` Prarit Bhargava
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=20161121174858.GB35881@redhat.com \
--to=dzickus@redhat.com \
--cc=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=johunt@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@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
Powered by JetHome