Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp3751727pxu; Sun, 11 Oct 2020 23:14:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxU/vmVLBmEXvwir3E/KtGqBdRd6nR4MEuXnu9WCZalkZbkurup77xX6ryctNtA951GAn73 X-Received: by 2002:aa7:c1da:: with SMTP id d26mr12117664edp.135.1602483289045; Sun, 11 Oct 2020 23:14:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602483289; cv=none; d=google.com; s=arc-20160816; b=0V0oCS53ar0HM+1yjf2SlcDQOh/6fy5KvZlHJJDp5lV+/5mdJrF7BKAOYiKyt0J5yR uRTqvDhi2TFDb2bnrSn73d3eJXnSQ5xRdlckoAeW7Ah4LBjSVJicsGlxwCQg4iJV8YJF C1NwTTFNmppW6bFUyDrOHq0akdTqmaJQ4vouEI7VQnTKgOOl2xCGlENtoucSN2th4gcF 8AxmEZSCP3ZEN54bzrJJYEt8pfoqztX9i4wLiOKgvcJv8aqNsDPuzGWTGINh1LFsKXwL Skq/WZEdkNRZP558qxq1vgxHuvuNUxTA9ge6k3zeJ6runsdQabXaaECdTBfwtmzDEf0y c+fQ== 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 :in-reply-to:mime-version:user-agent:date:message-id:references:cc :to:from:subject:ironport-sdr:ironport-sdr; bh=rzoVX4VOVlgo1zLAUkWxVZErBHe9D60+gEXK33RLf/s=; b=NmkB3iFa3LX3HZxzInlsZwrjwpSN1T205zv1l4HtJnWUGFUfqp6ur1BXHoHWuD4IvL pSVL7m95I+PdHkqZCoyWf6feHZ8lz328PahX5F1OyZ8a36KRNpU+ZPKK6r03igD8Cr92 m/tcPNBLHJJg7cTgQNkbfXDaaBD0ycsG+j7+emciTWZGKPdZ+9vsR5llXCUBjkNrHQ6c ea1Tt1tz7f1WJkFAjXXYVwrtxuHdgLgPUoUME6N6ebmW/6b0yOTY6Olp1NowPDFQkYo6 /KN2eK4GdyLJ6fYFCSUkKV8xk4h3wPmON5UhRnEQGKsVR5PRxL7IiKnMGNc+HJUvte5P tZdA== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id si11si11320252ejb.693.2020.10.11.23.14.26; Sun, 11 Oct 2020 23:14:49 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726584AbgJLFN5 (ORCPT + 99 others); Mon, 12 Oct 2020 01:13:57 -0400 Received: from mga14.intel.com ([192.55.52.115]:24006 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725967AbgJLFN5 (ORCPT ); Mon, 12 Oct 2020 01:13:57 -0400 IronPort-SDR: 7ADqcn1ok1sE6gxqAUEE+ZlRYBjKx3YmtCNLjxnar6tJXiuy5pHh0JM+VdSrs0DdwDLiyGgZTn 8zqZ+YmU8eXg== X-IronPort-AV: E=McAfee;i="6000,8403,9771"; a="164905262" X-IronPort-AV: E=Sophos;i="5.77,365,1596524400"; d="scan'208";a="164905262" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Oct 2020 22:13:57 -0700 IronPort-SDR: XIJncUnAd3RoeChaxJorWzxcTwLLSIoVmhAwwlmHM8se+NpLFZWPSyKs3VPtk5ESjbtuhiXdC7 DdEXSY15TSpQ== X-IronPort-AV: E=Sophos;i="5.77,365,1596524400"; d="scan'208";a="355679494" Received: from sdhopkin-mobl.amr.corp.intel.com (HELO [10.254.98.243]) ([10.254.98.243]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Oct 2020 22:13:56 -0700 Subject: Re: [PATCH v3 1/1] PCI/ERR: Fix reset logic in pcie_do_recovery() call From: "Kuppuswamy, Sathyanarayanan" To: Sinan Kaya , Bjorn Helgaas Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, ashok.raj@intel.com, Jay Vosburgh References: <20200922233333.GA2239404@bjorn-Precision-5520> <526dc846-b12b-3523-4995-966eb972ceb7@kernel.org> <1fdcc4a6-53b7-2b5f-8496-f0f09405f561@linux.intel.com> <95e23cb5-f6e1-b121-0de8-a2066d507d9c@linux.intel.com> <65238d0b-0a39-400a-3a18-4f68eb554538@kernel.org> <4ae86061-2182-bcf1-ebd7-485acf2d47b9@linux.intel.com> <8beca800-ffb5-c535-6d43-7e750cbf06d0@linux.intel.com> <44f0cac5-8deb-1169-eb6d-93ac4889fe7e@kernel.org> <3bc0fd23-8ddd-32c5-1dd9-4d5209ea68c3@linux.intel.com> <8a3aeb3c-83c4-8626-601d-360946d55dd8@linux.intel.com> <9b295cad-7302-cf2c-d19d-d27fabcb48be@kernel.org> <93b4015f-df2b-728b-3ef7-ac5aa10f03ed@kernel.org> Message-ID: <0013f3d2-569a-27ba-336e-3d4668834545@linux.intel.com> Date: Sun, 11 Oct 2020 22:13:54 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sinan, On 9/28/20 11:32 AM, Kuppuswamy, Sathyanarayanan wrote: > > > On 9/28/20 11:25 AM, Sinan Kaya wrote: >> On 9/28/2020 2:02 PM, Sinan Kaya wrote: >>> Since there is no state restoration for FATAL errors, I am wondering >>> whether >>> calls to ->error_detected(), ->mmio_enabled() and ->slot_reset() are >>> required? >> >> I also would like to ask someone closer to the spec language double >> check this. >> >> When we recover the link at the end of the DPC handler, what is the >> expected state of the endpoint? >> >> Is it a some kind of a reset like secondary bus reset? (I assumed this >>   one) > I think it will be in reset state. >> >> Undefined? >> >> or just plain link recovery with everything else as intact as it used >> to be? >> > Please check the following version. It should fix most of the reset issues properly. https://lore.kernel.org/linux-pci/5c5bca0bdb958e456176fe6ede10ba8f838fbafc.1602263264.git.sathyanarayanan.kuppuswamy@linux.intel.com/T/#t -- Sathyanarayanan Kuppuswamy Linux Kernel Developer