Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp654496pxf; Wed, 17 Mar 2021 12:34:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyqRxd8MAImlX9OujX9l6Oo2cgH2731892Yn1TYkGmz5uy2Q7nIYajobcMdowflOHd+/mlR X-Received: by 2002:a17:906:aac5:: with SMTP id kt5mr37783818ejb.548.1616009698146; Wed, 17 Mar 2021 12:34:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616009698; cv=none; d=google.com; s=arc-20160816; b=mrhStr9lv5qdTlp1JsjSO/ew/wZ/YGC3Q5MmWB2f60VBzxTrpl5pgpEA0tA8TvhZ3h Uhom5oh8Hk0W37zurh7A/r+dSk+IEHTY8HG8RoSumUqrVcnDq2U/xRFw1y4C+wOQZUOi 3VayOMFJp4Eb8edJkz+98NxRnRPU6YFQMSZUa4hwaqsyLpJkDTFdRPJKwMb988hkjH5q TwmAPESh92lrnzKiYzBrVn8CqoMfiIUyzDYInH9fgJjXHWy4JcN3isU+e1G+nF1ODfyl xTriajxOmA5RBRS5aAwFES604378SsE+Xk5Io3tRuDRkUADQtltOQNjbR/VZl/olUWvS EDIA== 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 :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=PdAQqv2znUyJGHKP0rUSqIjMCYDHVuDQjM9e5TLBxfo=; b=k0w3lx9/JduTzQk2fRcmjdjgy8I/BQ77c4bvmPqT4rvaxo+UnhWybvaz7M1GjUtI2b R9ZqFpkQ7cXTKeXklzCnYp2PFCyayel2utSZsdQP/bDFERRpXkv4uSLeNpL3iasMK8X2 aLKqzJIVizMPoXiGOJn9V3DkW6qr2Nc7BdlwgNCnTlyTTA3ZIFT+cxA1RTOTPrUCeabf 7THi9KqwjYrAW6y3BzYOhPI7fkEaNIA/59OFZUuksuIOYWUB6SkvZ2npvrIwBgqw7c+r DrlkeeEpenH5aOwkgNfH4e5aiyjaqVq64ccBw9Ksema/Juz54eH2t6rxF3u9pbcV80Pm l7Ww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="S3b9Ut/X"; 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g12si15884571ejd.256.2021.03.17.12.34.15; Wed, 17 Mar 2021 12:34:58 -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=@redhat.com header.s=mimecast20190719 header.b="S3b9Ut/X"; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232120AbhCQTdQ (ORCPT + 99 others); Wed, 17 Mar 2021 15:33:16 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:23449 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233191AbhCQTcv (ORCPT ); Wed, 17 Mar 2021 15:32:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616009569; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PdAQqv2znUyJGHKP0rUSqIjMCYDHVuDQjM9e5TLBxfo=; b=S3b9Ut/XVQnrukoyLkPyu5cyyMait4O7MGdoiXWeHFYCkzlEnBABvfZdmlQQuWjZDE/WS/ 6JaXDamjyutUfm2YOA3letc7gfg7wlBZtUntq9F4WMjltwHdCpI4arEL8M9mLsmBoVr9JQ AcYOiCcOnUt6Be+twThxlgCHeFAe8CQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-402-Q51B6FILMMSWnsfeKv5N0A-1; Wed, 17 Mar 2021 15:32:47 -0400 X-MC-Unique: Q51B6FILMMSWnsfeKv5N0A-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8B02481425A; Wed, 17 Mar 2021 19:32:46 +0000 (UTC) Received: from omen.home.shazbot.org (ovpn-112-255.phx2.redhat.com [10.3.112.255]) by smtp.corp.redhat.com (Postfix) with ESMTP id 1EC1A5D9C0; Wed, 17 Mar 2021 19:32:46 +0000 (UTC) Date: Wed, 17 Mar 2021 13:32:45 -0600 From: Alex Williamson To: Pali =?UTF-8?B?Um9ow6Fy?= 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: <20210317133245.7d95909c@omen.home.shazbot.org> In-Reply-To: <20210317192424.kpfybcrsen3ivr4f@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> <20210315145238.6sg5deblr2z2pupu@pali> <20210315090339.54546e91@x1.home.shazbot.org> <20210317190206.zrtzwgskxdogl7dz@pali> <20210317131536.38f398b0@omen.home.shazbot.org> <20210317192424.kpfybcrsen3ivr4f@pali> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 17 Mar 2021 20:24:24 +0100 Pali Roh=C3=A1r wrote: > On Wednesday 17 March 2021 13:15:36 Alex Williamson wrote: > > On Wed, 17 Mar 2021 20:02:06 +0100 > > Pali Roh=C3=A1r wrote: > > =20 > > > On Monday 15 March 2021 09:03:39 Alex Williamson wrote: =20 > > > > On Mon, 15 Mar 2021 15:52:38 +0100 > > > > Pali Roh=C3=A1r wrote: > > > > =20 > > > > > On Monday 15 March 2021 08:34:09 Alex Williamson wrote: =20 > > > > > > On Mon, 15 Mar 2021 14:52:26 +0100 > > > > > > Pali Roh=C3=A1r wrote: > > > > > > =20 > > > > > > > On Monday 15 March 2021 19:13:23 Amey Narkhede wrote: =20 > > > > > > > > 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. =20 > > > > > > >=20 > > > > > > > No. PCI secondary bus reset =3D PCIe Hot Reset. Slot reset is= just another > > > > > > > type of reset, which is currently implemented only for PCIe h= ot 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). =20 > > > > > >=20 > > > > > > Warm reset is beyond the scope of this series, but could be imp= lemented > > > > > > in a compatible way to fit within the pci_reset_fn_methods[] ar= ray > > > > > > defined here. =20 > > > > >=20 > > > > > Ok! > > > > > =20 > > > > > > Note that with this series the resets available through > > > > > > pci_reset_function() and the per device reset attribute is sysf= s remain > > > > > > exactly the same as they are currently. The bus and slot reset > > > > > > methods used here are limited to devices where only a single fu= nction is > > > > > > affected by the reset, therefore it is not like the patch you p= roposed > > > > > > which performed a reset irrespective of the downstream devices.= This > > > > > > series only enables selection of the existing methods. Thanks, > > > > > >=20 > > > > > > Alex > > > > > > =20 > > > > >=20 > > > > > But with this patch series, there is still an issue with PCI seco= ndary > > > > > 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. =20 > > > >=20 > > > > No, there's not: > > > >=20 > > > > int pci_reset_function(struct pci_dev *dev) > > > > { > > > > int rc; > > > >=20 > > > > if (!dev->reset_fn) > > > > return -ENOTTY; > > > >=20 > > > > pci_dev_lock(dev); =20 > > > > >>> pci_dev_save_and_disable(dev); =20 > > > >=20 > > > > rc =3D __pci_reset_function_locked(dev); > > > > =20 > > > > >>> pci_dev_restore(dev); =20 > > > > pci_dev_unlock(dev); > > > >=20 > > > > return rc; > > > > } > > > >=20 > > > > The remove/re-scan was discussed primarily because your patch perfo= rmed > > > > a bus reset regardless of what devices were affected by that reset = and > > > > it's difficult to manage the scope where multiple devices are affec= ted. > > > > Here, the bus and slot reset functions will fail unless the scope is > > > > limited to the single device triggering this reset. Thanks, > > > >=20 > > > > Alex > > > > =20 > > >=20 > > > I was thinking a bit more about it and I'm really sure how it would > > > behave with hotplugging PCIe bridge. > > >=20 > > > On aardvark PCIe controller I have already tested that secondary bus > > > reset bit is triggering Hot Reset event and then also Link Down event. > > > These events are not handled by aardvark driver yet (needs to > > > implemented into kernel's emulated root bridge code). > > >=20 > > > But I'm not sure how it would behave on real HW PCIe hotplugging brid= ge. > > > Kernel has already code which removes PCIe device if it changes prese= nce > > > bit (and inform via interrupt). And Link Down event triggers this > > > change. =20 > >=20 > > This is the difference between slot and bus resets, the slot reset is > > implemented by the hotplug controller and disables presence detection > > around the bus reset. Thanks, =20 >=20 > Yes, but I'm talking about bus reset, not about slot reset. >=20 > I mean: to use bus reset via sysfs on hardware which supports slots and > hotplugging. >=20 > And if I'm reading code correctly, this combination is allowed, right? > Via these new patches it is possible to disable slot reset and enable > bus reset. That's true, a slot reset is simply a bus reset wrapped around code that prevents the device from getting ejected. Maybe it would make sense to combine the two as far as this interface is concerned, ie. a single "bus" reset method that will always use slot reset when available. Thanks, Alex