From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9434BC4167B for ; Tue, 29 Nov 2022 16:06:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235850AbiK2QGy (ORCPT ); Tue, 29 Nov 2022 11:06:54 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235975AbiK2QGb (ORCPT ); Tue, 29 Nov 2022 11:06:31 -0500 Received: from bmailout2.hostsharing.net (bmailout2.hostsharing.net [83.223.78.240]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9514513F46 for ; Tue, 29 Nov 2022 08:06:28 -0800 (PST) Received: from h08.hostsharing.net (h08.hostsharing.net [83.223.95.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.hostsharing.net", Issuer "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by bmailout2.hostsharing.net (Postfix) with ESMTPS id AC86D2800C982; Tue, 29 Nov 2022 17:06:26 +0100 (CET) Received: by h08.hostsharing.net (Postfix, from userid 100393) id A1068173A43; Tue, 29 Nov 2022 17:06:26 +0100 (CET) Date: Tue, 29 Nov 2022 17:06:26 +0100 From: Lukas Wunner To: Alex Williamson Cc: Mika Westerberg , Bjorn Helgaas , Bjorn Helgaas , linux-pci@vger.kernel.org Subject: Re: PCI resource allocation mismatch with BIOS Message-ID: <20221129160626.GA19822@wunner.de> References: <20221128203932.GA644781@bhelgaas> <20221128150617.14c98c2e.alex.williamson@redhat.com> <20221129064812.GA1555@wunner.de> <20221129065242.07b5bcbf.alex.williamson@redhat.com> <20221129084646.0b22c80b.alex.williamson@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221129084646.0b22c80b.alex.williamson@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Tue, Nov 29, 2022 at 08:46:46AM -0700, Alex Williamson wrote: > Maybe the elephant in the room is why it's apparently such common > practice to need to perform a hard reset these devices outside of > virtualization scenarios... These GPUs are used as accelerators in cloud environments. They're reset to a pristine state when handed out to another tenant to avoid info leaks from the previous tenant. That should be a legitimate usage of PCIe reset, no? Thanks, Lukas