Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752758AbdF2QgL (ORCPT ); Thu, 29 Jun 2017 12:36:11 -0400 Received: from mga01.intel.com ([192.55.52.88]:49741 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751695AbdF2QgE (ORCPT ); Thu, 29 Jun 2017 12:36:04 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,281,1496127600"; d="scan'208";a="105231137" Date: Thu, 29 Jun 2017 09:36:03 -0700 From: Andi Kleen To: Don Zickus Cc: "Liang, Kan" , Thomas Gleixner , "linux-kernel@vger.kernel.org" , "mingo@kernel.org" , "akpm@linux-foundation.org" , "babu.moger@oracle.com" , "atomlin@redhat.com" , "prarit@redhat.com" , "torvalds@linux-foundation.org" , "peterz@infradead.org" , "eranian@google.com" , "acme@redhat.com" , "stable@vger.kernel.org" Subject: Re: [PATCH V2] kernel/watchdog: fix spurious hard lockups Message-ID: <20170629163603.GO23705@tassilo.jf.intel.com> References: <20170626201927.3ak7fk3yvdzbb4ay@redhat.com> <20170627201249.ll34ecwhpme3vh2u@redhat.com> <37D7C6CF3E00A74B8858931C1DB2F0775371357D@SHSMSX103.ccr.corp.intel.com> <20170627234822.GL23705@tassilo.jf.intel.com> <20170628190008.3ftqq75evhn2hozp@redhat.com> <20170628201404.GM23705@tassilo.jf.intel.com> <20170629154406.44xo7dnw7btn4gpx@redhat.com> <20170629161220.GN23705@tassilo.jf.intel.com> <20170629162618.exjllikxeac3ujih@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170629162618.exjllikxeac3ujih@redhat.com> User-Agent: Mutt/1.8.0 (2017-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 350 Lines: 9 > > Thomas' patch to modulate the frequency seemed reasonable to me. > > It made the NMI watchdog depend on accurate ktime, but that's probably ok. > > Ok, did Kan finish testing this patch (with the small fix on top)? Kan doesn't have the specific hardware to test it. We've been waiting for another team to do the testing. I'll ping them. -Andi