Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1780036pxj; Sun, 30 May 2021 03:11:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw1ir/L9yEv3mlxGmIaioHMxH3RyoaSaoTv3ZhrV+BdrFdJO8LheyjZiifUaawPitMZgyiw X-Received: by 2002:aa7:c9cf:: with SMTP id i15mr19231109edt.118.1622369494910; Sun, 30 May 2021 03:11:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622369494; cv=none; d=google.com; s=arc-20160816; b=Ww26WukXJl6BPBUAkwCQib3PIl7xzY+qLB2tv5hmDVTY2aP1TFVevZ3hs7hZARQHKl hAUgHdYIrwqHRUyAhvBuZOItgucY9lrkD+G1oTUKHdC8feKwL1l3qoL/SNf7I2pTprAv XlE40W+ycxxC+3y+J3vG5yKy6+Hg3tM6KZsddXNDoMXfukUUMMd0m522hzFXhl4/omz4 Gmk6AOxT2rAiqsOenSs/yZPPKOg5TrUfdYnf2SnCfyXsBgBj4xaBz3ilflptFBdDokfw JqJFt9+cML35txZ9yFNcJmIU08bYcm/X8wx7z7+n8RIuEXTZdD875n2C6Qj8+/9syGZr zExQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :mime-version:user-agent:date:message-id:cc:to:subject:from; bh=iH7homDANNyZureQWg5inCWWpfgSr4ZdO4vQ6776qk0=; b=0hnxWfGFMkX+jwHfikqg0otPrQf33k7j40Qrvrp+U9P44lN7QIZEDFngb9BNBJ8fsp dpYcTJ2Xiq26C462D0pVvptEtHrZNC3QzxtzfVoK7m0uYm1wRv9ideexzt/2+XCJieKG 1L6U0wikKhBD6u9ZGxcZBiJqRUR+0NHHoUBbYOEn4SHrwPaJtNCj2T1GZ553RAt5lJlO ojQgDieGVxeD0jKJAZT5hlgaOAqA4OW4wNjfH6x69u1VMAcNkRI8VnH0s98O3E03Fb8v 0/ndnszin/wnq2d6vAXX2jRFTBX3e25T0OHu1Za1KsAV+c9CGSI0hjtjQogt94azeYVS JFbw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n15si9656434edt.229.2021.05.30.03.10.59; Sun, 30 May 2021 03:11:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229617AbhE3KHr (ORCPT + 99 others); Sun, 30 May 2021 06:07:47 -0400 Received: from gecko.sbs.de ([194.138.37.40]:35904 "EHLO gecko.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229500AbhE3KHq (ORCPT ); Sun, 30 May 2021 06:07:46 -0400 X-Greylist: delayed 407 seconds by postgrey-1.27 at vger.kernel.org; Sun, 30 May 2021 06:07:45 EDT Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 14U9wufY030721 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 30 May 2021 11:58:56 +0200 Received: from [167.87.72.222] ([167.87.72.222]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 14U9wtEv030019; Sun, 30 May 2021 11:58:55 +0200 From: Jan Kiszka Subject: [PATCH] watchdog: iTCO_wdt: Account for rebooting on second timeout To: Wim Van Sebroeck , Guenter Roeck Cc: linux-watchdog@vger.kernel.org, Linux Kernel Mailing List , Paolo Bonzini , Christian Storm , Andy Shevchenko Message-ID: <73a36792-28f8-e513-b384-bdbe7d31ca05@siemens.com> Date: Sun, 30 May 2021 11:58:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jan Kiszka This was already attempted to fix via 1fccb73011ea: If the BIOS did not enable TCO SMIs, the timer definitely needs to trigger twice in order to cause a reboot. If TCO SMIs are on, we can continue to assume that the BIOS will perform a reboot on the first timeout. QEMU with its ICH9 and related BIOS falls into the former category, currently taking twice the configured timeout in order to reboot the machine. For iTCO version that fall under turn_SMI_watchdog_clear_off, this is also true and was currently only addressed for v1, irrespective of the turn_SMI_watchdog_clear_off value. Signed-off-by: Jan Kiszka --- drivers/watchdog/iTCO_wdt.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c index bf31d7b67a69..091797d12146 100644 --- a/drivers/watchdog/iTCO_wdt.c +++ b/drivers/watchdog/iTCO_wdt.c @@ -71,6 +71,7 @@ #define TCOBASE(p) ((p)->tco_res->start) /* SMI Control and Enable Register */ #define SMI_EN(p) ((p)->smi_res->start) +#define TCO_EN (1 << 13) #define TCO_RLD(p) (TCOBASE(p) + 0x00) /* TCO Timer Reload/Curr. Value */ #define TCOv1_TMR(p) (TCOBASE(p) + 0x01) /* TCOv1 Timer Initial Value*/ @@ -355,8 +356,11 @@ static int iTCO_wdt_set_timeout(struct watchdog_device *wd_dev, unsigned int t) tmrval = seconds_to_ticks(p, t); - /* For TCO v1 the timer counts down twice before rebooting */ - if (p->iTCO_version == 1) + /* + * If TCO SMIs are off, the timer counts down twice before rebooting. + * Otherwise, the BIOS generally reboots when the SMI triggers. + */ + if (p->smi_res && !(SMI_EN(p) & TCO_EN)) tmrval /= 2; /* from the specs: */ @@ -521,7 +525,7 @@ static int iTCO_wdt_probe(struct platform_device *pdev) * Disables TCO logic generating an SMI# */ val32 = inl(SMI_EN(p)); - val32 &= 0xffffdfff; /* Turn off SMI clearing watchdog */ + val32 &= ~TCO_EN; /* Turn off SMI clearing watchdog */ outl(val32, SMI_EN(p)); } -- 2.26.2