Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4427860pxf; Tue, 30 Mar 2021 07:36:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzC5Ze9RfqvetJCcZGX+lrYGktpfAO7Bcon3y6LwgvWpXApvCcH/Fmk4A5WYsqb6y3eumJ3 X-Received: by 2002:a17:906:85b:: with SMTP id f27mr34209604ejd.414.1617115002902; Tue, 30 Mar 2021 07:36:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617115002; cv=none; d=google.com; s=arc-20160816; b=hvlZJpzC+VGaOqzzHMXsJoduqQQU5Ecwym0OBFMO+X+ugErmXPgSmd+aWH00wcGWi2 aRq8c/v9c0w/1joncGz7FxLi2Ck2pVkbsWOskai6f8/CoVhsoGJER+hox2a0Dsx0p40m bmdkiUsQqVoww+zX672IO+66HzT0UqfRgPdW6VU2k/ul0tjVzrqRq+m4O9ET1ihwT1T3 KI7SmUXircsdy9nidgACnBKJgQPNM7WCNPzGh9JwYOdwwgwCpd+/hLryhFQIdngoUE6n jbRuu7PYyO4WNH1Y/ghRXv7Jy3XXFwms6rqKPPyLFUy8a2D73cVn2wrYT5H+RyLUesoP g6+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:message-id:in-reply-to:subject:cc:to:from :date; bh=YGiXyOe9ElPAhL7A6CSQaSrD3TPPVjc8pKZ0J5gtJIU=; b=doy3Jxks/0n0aK87AGrAdMtwRVscdomFu9pPX7e/ujoCfmtx5LMu3fDPPNFCa30rvS JdjftKSX5OPguXIP80dit5mmNNKAqukf950jWPWZTxuqwH1UOl4RNBsY6Nc7DEU6eqha 7ICGwYzAzYVfwulW7CxU/lmplqajWZ6YCuhYy3b5uca3J+pLyaoRWhtjD5qsoP2vRzkV Kc2y0iJhRxRtQgTUqEIRg/ZWZwy9usjpgidb3o/fCjUNN5MvlMlHPDuBjPqKTCEwyuIi yg+DugPkne9aoEHtjVvxSj0ghgVCRNhszN5zbDK6I7WtbIOPe/7X1Gq4k+KvmRc+ee5T l9rg== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f25si15674686edr.248.2021.03.30.07.36.19; Tue, 30 Mar 2021 07:36:42 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231942AbhC3OfA (ORCPT + 99 others); Tue, 30 Mar 2021 10:35:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232067AbhC3Oet (ORCPT ); Tue, 30 Mar 2021 10:34:49 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::4]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id DAA95C061574; Tue, 30 Mar 2021 07:34:48 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 8764492009C; Tue, 30 Mar 2021 16:34:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 7FDA592009B; Tue, 30 Mar 2021 16:34:47 +0200 (CEST) Date: Tue, 30 Mar 2021 16:34:47 +0200 (CEST) From: "Maciej W. Rozycki" To: =?UTF-8?Q?Pali_Roh=C3=A1r?= cc: David Laight , 'Amey Narkhede' , "alex.williamson@redhat.com" , "helgaas@kernel.org" , "lorenzo.pieralisi@arm.com" , "kabel@kernel.org" , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "raphael.norwitz@nutanix.com" Subject: Re: How long should be PCIe card in Warm Reset state? In-Reply-To: <20210330131018.gby4ze3u6mii23ls@pali> Message-ID: References: <20210310110535.zh4pnn4vpmvzwl5q@pali> <20210323161941.gim6msj3ruu3flnf@archlinux> <20210323162747.tscfovntsy7uk5bk@pali> <20210323165749.retjprjgdj7seoan@archlinux> <20210330131018.gby4ze3u6mii23ls@pali> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Mar 2021, Pali Rohár wrote: > > If I were to implement this stuff, for good measure I'd give it a safety > > margin beyond what the spec requires and use a timeout of say 2-4s while > > actively querying the status of the device. The values given in the spec > > are only the minimum requirements. > > Are you able to also figure out what is the minimal timeout value for > PCIe Warm Reset? > > Because we are having troubles to "decode" correct minimal timeout value > for this PCIe Warm Reset (not Function-level reset). The spec does not give any exceptions AFAICT as to the timeouts required between the three kinds of a Conventional Reset (Hot, Warm, or Cold) and refers to them collectively as a Conventional Reset across the relevant parts of the document, so clearly the same rules apply. Maciej