From: Don Zickus <dzickus@redhat.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"babu.moger@oracle.com" <babu.moger@oracle.com>,
"atomlin@redhat.com" <atomlin@redhat.com>,
"prarit@redhat.com" <prarit@redhat.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"eranian@google.com" <eranian@google.com>,
"acme@redhat.com" <acme@redhat.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] kernel/watchdog: fix spurious hard lockups
Date: Wed, 21 Jun 2017 09:47:47 -0400 [thread overview]
Message-ID: <20170621134747.kd6w5rq4zforzaad@redhat.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07753710034@SHSMSX103.ccr.corp.intel.com>
On Wed, Jun 21, 2017 at 12:40:28PM +0000, Liang, Kan wrote:
>
> > >
> > > The right fix for mainline can be found here.
> > > perf/x86/intel: enable CPU ref_cycles for GP counter perf/x86/intel,
> > > watchdog: Switch NMI watchdog to ref cycles on x86
> > > https://patchwork.kernel.org/patch/9779087/
> > > https://patchwork.kernel.org/patch/9779089/
> >
> > Presumably the "right fix" will later be altered to revert this one-line
> > workaround?
>
> The "right fix" itself will not touch the watchdog rate. I will modify the
> changelog to notify the people who want to do the backport.
>
> As my understanding, it's not harmful even if we don't revert the
> workaround. It can still detect the hardlockup, only takes
> a tiny bit longer.
It depends on you perspective of harmful. :-) There are folks that would
like that sampling rate to be more accurate, so they can detect problems
soon than later. You just took an input of 'watchdog_thresh' and blindly
multiplied it by 3, which can confuse an end user who thought they setup a 5
second threshold but instead it turned into a 15 second one. :-(
Cheers,
Don
next prev parent reply other threads:[~2017-06-21 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:33 kan.liang
2017-06-20 22:03 ` Andrew Morton
2017-06-21 12:40 ` Liang, Kan
2017-06-21 13:47 ` Don Zickus [this message]
2017-06-21 14:10 ` Liang, Kan
2017-06-20 22:34 ` Prarit Bhargava
2017-06-20 23:00 ` Andi Kleen
2017-06-21 0:12 ` Prarit Bhargava
2017-06-21 21:02 ` Marc Herbert
2017-06-21 13:40 ` Don Zickus
2017-06-21 14:02 ` Liang, Kan
2017-06-28 11:40 ` Michal Hocko
2017-06-28 13:24 ` Liang, Kan
2017-06-28 14:29 ` Michal Hocko
2017-06-28 14:32 ` Liang, Kan
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=20170621134747.kd6w5rq4zforzaad@redhat.com \
--to=dzickus@redhat.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=babu.moger@oracle.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®