Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3372958pxf; Mon, 15 Mar 2021 08:11:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzJPPL/RYrKZw4AzqQXHCAQH2XVrm1oe++CCSUAVTkcVpHCLGLfgWYQ2yl+9KldKlCPjnTK X-Received: by 2002:a17:906:ecf3:: with SMTP id qt19mr23773706ejb.467.1615821088434; Mon, 15 Mar 2021 08:11:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1615821088; cv=none; d=google.com; s=arc-20160816; b=Z1TikLfqlWgAoAm9LQHIxZCXwhfjuEXncXdNjp9zL2C2Eveoi3qSipc4LfiGQmtwdt t803DqXI9cskbhTcyiRuolGG5gx8Bv9AwYr1CrCDuNfkirx4S8q9HVMjW+Kpe5P7rbip dlgD4ruYHCptLHzFURK0VZhWMzhQrF6vDBrE15kG1W1Np2LjSa7kwrKXJqbfsMM6Fuin WDNVaaDBIKnwnRLw5eJQI6n9X/Jvu8orinO6aTcULarPhPkgosGS3lAcMbkgQcy15GVY 738072NbHm3SFRjlGk42T8+pMhCI2IOjlUT0AWeWrTfb3Ogi3GWp80DFYuVeLq1m4Il+ pDvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=NyHxzo7kJFYIfGWcDRIdgxPftKPLNJQ6nVfoIpggGJU=; b=dgplf+mlR/adPRCQxX6Hr2RQkJx5I8vfFNSxbtD5HmuvzsqTaJp2b5ODV8M+sjOqKH gT6TCYRyMf7nv0+7wk0tt8Rm8D/7yEF08z4emk0IOA7rzGC83fad608zZp+wUrSPsHxP fr1nLjzNRpEmkRh81hCrMSGbWCTYei4M5FCesRGvGdPzt3yLmbXGX21bbTqpyh5MAurv H/x1tO6i98skllG5zRtCsWWDpmrvPmyjR71mLCqvlGVRGb8qEpYCWz9yduZhS119/ZC0 /NwaZGUZYwDCaOSmoXdYJ0md9xHQXPxwo32A91KxLYlNz9F9k/K5F8Va3Qf6QaJounOG OEPw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=IsiINWnE; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bs6si11025177edb.145.2021.03.15.08.11.03; Mon, 15 Mar 2021 08:11:28 -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=@kernel.org header.s=k20201202 header.b=IsiINWnE; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231313AbhCOPIG (ORCPT + 99 others); Mon, 15 Mar 2021 11:08:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:51572 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237909AbhCOPHS (ORCPT ); Mon, 15 Mar 2021 11:07:18 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4420664DDF; Mon, 15 Mar 2021 15:07:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615820838; bh=XWtY5TrlDj205yMxswmssJtQpzPjqYZvnSFgDjHYf3Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IsiINWnEUVxh+ebkcsJHKfr1UHle02AB79BC4Ecuj470m0d1FrlR0Vv1w73TFnarl vPhjPAeRL7y06AhpBr7n0E1amh+ULFyWc4vlsXPzK+Dr4v0iFhtRZLYcnUYMMgAnqD Zp77IH5tUNHqJ3uYI+VmBHv2uNWz/WMeW/56H304AmsmmDQTZu5RySaZSN7ZxGSfrH yd0NYnprVK1eex+/tnL2NaITJjOn+kLbe1DFodiG26/TXdi+gXeX864uw2HKaA1ESP 6Nof9zsC7bg9chj+/B3GZe93PzmWOFa9GvbDCReGcvTQ4hBM+QGp7eTbtMLrqi6MpE 6ABtBg/T1S6wA== Date: Mon, 15 Mar 2021 17:07:14 +0200 From: Leon Romanovsky To: Alex Williamson Cc: Pali =?iso-8859-1?Q?Roh=E1r?= , Amey Narkhede , bhelgaas@google.com, raphael.norwitz@nutanix.com, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH 4/4] PCI/sysfs: Allow userspace to query and set device reset mechanism Message-ID: References: <20210312173452.3855-1-ameynarkhede03@gmail.com> <20210312173452.3855-5-ameynarkhede03@gmail.com> <20210314235545.girtrazsdxtrqo2q@pali> <20210315134323.llz2o7yhezwgealp@archlinux> <20210315135226.avwmnhkfsgof6ihw@pali> <20210315083409.08b1359b@x1.home.shazbot.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210315083409.08b1359b@x1.home.shazbot.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 15, 2021 at 08:34:09AM -0600, Alex Williamson wrote: > On Mon, 15 Mar 2021 14:52:26 +0100 > Pali Roh?r wrote: > > > On Monday 15 March 2021 19:13:23 Amey Narkhede wrote: > > > slot reset (pci_dev_reset_slot_function) and secondary bus > > > reset(pci_parent_bus_reset) which I think are hot reset and > > > warm reset respectively. > > > > No. PCI secondary bus reset = PCIe Hot Reset. Slot reset is just another > > type of reset, which is currently implemented only for PCIe hot plug > > bridges and for PowerPC PowerNV platform and it just call PCI secondary > > bus reset with some other hook. PCIe Warm Reset does not have API in > > kernel and therefore drivers do not export this type of reset via any > > kernel function (yet). > > Warm reset is beyond the scope of this series, but could be implemented > in a compatible way to fit within the pci_reset_fn_methods[] array > defined here. Note that with this series the resets available through > pci_reset_function() and the per device reset attribute is sysfs remain > exactly the same as they are currently. The bus and slot reset > methods used here are limited to devices where only a single function is > affected by the reset, therefore it is not like the patch you proposed > which performed a reset irrespective of the downstream devices. This > series only enables selection of the existing methods. Thanks, Alex, I asked the patch author here [1], but didn't get any response, maybe you can answer me. What is the use case scenario for this functionality? Thanks [1] https://lore.kernel.org/lkml/YE389lAqjJSeTolM@unreal > > Alex >