Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp418834pxk; Thu, 3 Sep 2020 03:19:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJynR5WasqyZJz/Ki3kBqW0oFyyXKIb7dj3po+rLVCxuA0DTQhy7amJpjaWhXbUFqdZl7QsS X-Received: by 2002:a17:906:b74a:: with SMTP id fx10mr1333671ejb.232.1599128376441; Thu, 03 Sep 2020 03:19:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599128376; cv=none; d=google.com; s=arc-20160816; b=e5SD+WNGOksQfU+wH8BXsEhlb/UAPmLB3eUbVrGanufYqz7llwDAzCJ7BSAng/wE/q wt8FJz4O0ZQxWTkPkUoGUIGyib9wYfDmyKXFzW3ZIzllZkg54vTIQMeLPiGu8CLYHt4W HJFlCMbikpZqVbZxEQI8WzqVHCrABdnLqFtV7aTYuh9XscVYU7d75+BRz18IVh/mNlkU r+6ZML5RLiU2Y6CinI+mBv/1fk0+vTKs2plIbIUNT1FaP4wnnq5LClmaeZk+Yte2TuhL tKwbHVSPUgr0GagQ4Mov8d6815GzqMNOyFVjcrjTab7IkIMGD/UmkSnIGBujTPW+pzxL Qhew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=3oe0/uwfq+QF2u4rpHv4uS8kRmaPVl3feMTrn0jrNpw=; b=XzNLX3IHgF9EeNiWXrRzAJ+hofvRf8N/SPMgY9NopPooOidDqJWuZOl2++egGCrAe3 jWP1+U1TAmViEtZRV2WlIS4/T+5yCPwpJQAqm2wg+ZmaPODGe0Gy3E1DxPqejVqnJ5V1 THcnmTuyyAqfkrG2t4hguZCELfwhzfzcVUq09ksb/hY9r1l+zjuHrBPkUIhIEYK4n1w1 2cQDeBYH8rSj/tR/DPdTkFM3Dz55N+4z12Uml6toY30pVM7WrjwlTgL8nFCNCqI1QNI5 10ELA2Ln4OtvOiATiNNs/K1Z9gDaQalxmp/93F3sFwMGvKwseOeZsYqZ0un69hrpreYa Fmvw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@yadro.com header.s=mta-01 header.b=bbycdTpB; 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=pass (p=NONE sp=NONE dis=NONE) header.from=yadro.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dp16si2356676ejc.17.2020.09.03.03.19.13; Thu, 03 Sep 2020 03:19:36 -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; dkim=pass header.i=@yadro.com header.s=mta-01 header.b=bbycdTpB; 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=pass (p=NONE sp=NONE dis=NONE) header.from=yadro.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728304AbgICKQK (ORCPT + 99 others); Thu, 3 Sep 2020 06:16:10 -0400 Received: from mta-02.yadro.com ([89.207.88.252]:56630 "EHLO mta-01.yadro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726162AbgICKQJ (ORCPT ); Thu, 3 Sep 2020 06:16:09 -0400 Received: from localhost (unknown [127.0.0.1]) by mta-01.yadro.com (Postfix) with ESMTP id 8FB6C542D3; Thu, 3 Sep 2020 10:16:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h= content-transfer-encoding:mime-version:user-agent:content-type :content-type:organization:references:in-reply-to:date:date:from :from:subject:subject:message-id:received:received:received; s= mta-01; t=1599128166; x=1600942567; bh=hG/MCAQyYQhX01WN0uxqTRhm0 5X7D7VyvjKq75g9WDY=; b=bbycdTpBLRJu2pBDE9tj07vJLkIu/5VPMjpUdbpK6 BJOg11EHh9Tr2TBwfXc0eCRJR9H6IVPys8U/tE6hwQxAOgzO1cU8YpMF1vXq4LPb edqCyE2gFqfE1BiV6Yz9Es/gTmEbi6JCI6FGDNS6wbxcSZJ923vuAV3KCmxAN07b cI= X-Virus-Scanned: amavisd-new at yadro.com Received: from mta-01.yadro.com ([127.0.0.1]) by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aH_ZQYl4KLGb; Thu, 3 Sep 2020 13:16:06 +0300 (MSK) Received: from T-EXCH-02.corp.yadro.com (t-exch-02.corp.yadro.com [172.17.10.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mta-01.yadro.com (Postfix) with ESMTPS id C8DB350242; Thu, 3 Sep 2020 13:16:05 +0300 (MSK) Received: from localhost.localdomain (10.199.2.130) by T-EXCH-02.corp.yadro.com (172.17.10.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 3 Sep 2020 13:16:05 +0300 Message-ID: <6dd97c08809d576136d474f4b3f3b045a03634bb.camel@yadro.com> Subject: Re: watchdog start on restart From: Ivan Mikhaylov To: Christophe Leroy CC: Wim Van Sebroeck , Guenter Roeck , , Date: Thu, 3 Sep 2020 13:19:28 +0300 In-Reply-To: References: Organization: YADRO Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.199.2.130] X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To T-EXCH-02.corp.yadro.com (172.17.10.102) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2020-09-02 at 15:19 +0200, Christophe Leroy wrote: > Isn't it the default expected behaviour for a watchdog ? It depends on hardware and system requirements. You may have not just one watchdog device. > "stop watchdog on restart" is there to keep things under control during > a wanted machine reboot/restart, while still having the watchdog do its > job on an unexpected restart. Yes, that's correct. > What would be the advantage of an ioctl() compared to the existing way ? You can control stop/start at any moment for any number of watchdog devices. Thanks.