Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3361642pxf; Mon, 15 Mar 2021 08:00:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxbet938eCmfmTtpTTEl59HnQP3O4alBy+5s13yGqUB0vQ1fjc0JxcKiEANRMujY3Nsg4sW X-Received: by 2002:a50:bb47:: with SMTP id y65mr31091866ede.305.1615820408115; Mon, 15 Mar 2021 08:00:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1615820408; cv=none; d=google.com; s=arc-20160816; b=m1ZYGsa1KCoQNGq7PSrHQvar0QsIM8yCVsN8wJCQSlNelSO9k+FXo6CXKj+kAcsaRq NGI1fIfnnuGWoBvyV7C7wROpOsgtm9SzSAS5M4Yd5pJyr6Ln4IJVVUA8NtKuyD7/boKr OAgbrGse6c/bEra/69wMV2Z9g+RRr5/GguOnyqqf71N06rFbXgJziA6279GN3yBNG/JS rmcdENq4mYlsUYXN/l+PJNgc+kEZA7H8XIOUm6uBxld8eiVe8/MSgRAt1RKuA3ql20vD lUznDF5DD/YYlwMuioX/Z6fl6iz1B4pp5lvBmH3Tk32ApyMOqzPxda0bFXXXzj9+MYiV OoKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=qeo/NQ0xjQ1uXjRzMyxSmDSdIIowSgu7/Cw5niT53g4=; b=QsSGvboSaJfOFH9eVqHyp6n3ycYck4pigHGEeBpe2ubeixKLiHuiAxtepvisPJILQK eLX9+qTW/5TYYKzSdwQG53iMowKhgdnsuR7O1oTVNMgvEUTFAJ228+wokMwgkPJpZpuw FPiIIcALRdThmpZF8L2JHQDAz60yDIi3OizRzn9eqybzOnlfMQBgdQ0ydj3AH1hji/Tr YyDX3sJO8IY9ieEH4M/kdROWs4xztLjiV4LZWhJzFgk25DR8tknisTzPjwGrrWt0nhIV GjXZVQhdb6I2J4+kOo2dJHMcljo4aSIKmtIi7IqXgjmKVDOOh/JsBDZIimHOA3BPkj9O TorQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=OVrJ2ZTA; 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.07.59.45; Mon, 15 Mar 2021 08:00:08 -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=OVrJ2ZTA; 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 S241802AbhCOOyw (ORCPT + 99 others); Mon, 15 Mar 2021 10:54:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:47434 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240806AbhCOOwm (ORCPT ); Mon, 15 Mar 2021 10:52:42 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id CEEB264E4D; Mon, 15 Mar 2021 14:52:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615819961; bh=G3ozJXmGXxAqgrO+D3whXaRr9LYu3Iu2YW+g7hNfPuo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OVrJ2ZTABExkLOf3T9pFk2hY164N3cDdTbU4yBvVpG2Ue5m1HjAjXktQ4GhdZcxTO y2ufICjjv42ebbx3yl5/2eRtgGJj0Z7QEXFD9fW2HClpFzkvuXG5jLVSEXjz+8PQAg uen2Y/yZaPmK/4SD+zERgnidBLItHlVSnkpSQT1sY6AuWcV5uvSDeEPQAB91Zkj8ES 4rWtL82GfDZDDd50I3rXsBa4AXMlz0ThGU1ku0NpmbfI0r6if0Qtx5brsvZeN1qzYq +XqhVs+zdwXe4GhJ0TpEzBLqTcMDt/vYBbCrAaeQw8vd4J8cRi9wvcVPX9giO2GSqu 2NiMtcbp7KROA== Received: by pali.im (Postfix) id 6538182E; Mon, 15 Mar 2021 15:52:38 +0100 (CET) Date: Mon, 15 Mar 2021 15:52:38 +0100 From: Pali =?utf-8?B?Um9ow6Fy?= To: Alex Williamson Cc: 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: <20210315145238.6sg5deblr2z2pupu@pali> 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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20210315083409.08b1359b@x1.home.shazbot.org> User-Agent: NeoMutt/20180716 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday 15 March 2021 08:34:09 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. Ok! > 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 > But with this patch series, there is still an issue with PCI secondary bus reset mechanism as exported sysfs attribute does not do that remove-reset-rescan procedure. As discussed in other thread, this reset let device in unconfigured / broken state.