Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1821085pxj; Sun, 30 May 2021 04:32:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzG8x7Yk3va1GnAxVrMEpbaqEV33b4sm+uL9StTNvjxTl3ofCf4flKf167tQYoGXtTIoggI X-Received: by 2002:a05:6602:72f:: with SMTP id g15mr13328635iox.5.1622374326293; Sun, 30 May 2021 04:32:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622374326; cv=none; d=google.com; s=arc-20160816; b=ZQTBXQ0XZuS87OOediwMgafJV99zgY3g9anYGzIycO46OSRdRHSspYQSlSHu+O632/ pEenRThigK80cC+P52nBQw0fM5zYT+fsB3cggKlHLbJwdgBjIcH5ne21Y+iqbFmpM3NG aqtXujFnpQwK25md1sXw1F/hPMwazdBALo3GAGWO6vI9jFG4dmSnuxHfin0vDnhDBRDt EiKQ8IWOuVKy8hRbouzVwSuF8jYGajAZdlf64ezLwFr4Vpre1aOstXONwZlX8ckX3LT/ IYJXJpsIJZq8lGw2F/x3bJlQ46n3DWr1RTyIypRlL6Pjct+Mv43PrP4lti/nEfFO/wMs dgpw== 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=b6o6G++STxRGAV8LgQSNb98GDngA9hOvhf02suW8dkI=; b=0GazczD8wMbpWKVcAvODS582NNPLb7UkRvNLlHZryp1Bm6cpnql76F+xYtV2Kjcc3l e5PR2VnxGRY/prVOshksSQe3Uo8aeMq1G9AdECLprRAmPlE6HbRYgIpyE5A/SM08L4Bk 6saariNm62KybgbVvPDI4Dgoqpt9qje/ONOyyN+eAXZo+dFp69RAN903TMCgkT68V5Y9 nT+/fpiV1cTJh7jq2/TByaJi8k40NhAgKfS2Gw+TmOQeg+213QYwwQMhMKsnYcrpPhbV 9D6C8cikFiIaL3S+FVf9oZGpLpH8dKhBYtgwyLzfaE5w1HknP5O6SrHdtHXAbfgV6wlG 48JA== 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 k7si5142572ilh.42.2021.05.30.04.31.38; Sun, 30 May 2021 04:32:06 -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 S229683AbhE3LaB (ORCPT + 99 others); Sun, 30 May 2021 07:30:01 -0400 Received: from gecko.sbs.de ([194.138.37.40]:36461 "EHLO gecko.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229500AbhE3LaB (ORCPT ); Sun, 30 May 2021 07:30:01 -0400 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 14UBS5jM012746 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sun, 30 May 2021 13:28:05 +0200 Received: from [139.22.32.8] ([139.22.32.8]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 14UBONLG031032; Sun, 30 May 2021 13:24:23 +0200 From: Jan Kiszka Subject: [PATCH v2] 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: <0b8bb307-d08b-41b5-696c-305cdac6789c@siemens.com> Date: Sun, 30 May 2021 13:24:23 +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, as well as SMIs in general, 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 --- Changes in v2: - consider GBL_SMI_EN as well drivers/watchdog/iTCO_wdt.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c index bf31d7b67a69..3f1324871cfd 100644 --- a/drivers/watchdog/iTCO_wdt.c +++ b/drivers/watchdog/iTCO_wdt.c @@ -71,6 +71,8 @@ #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 GBL_SMI_EN (1 << 0) #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 +357,12 @@ 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 | GBL_SMI_EN)) != (TCO_EN | GBL_SMI_EN)) tmrval /= 2; /* from the specs: */ @@ -521,7 +527,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