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 34BC9CCA47F for ; Tue, 12 Jul 2022 17:14:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232716AbiGLROq (ORCPT ); Tue, 12 Jul 2022 13:14:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57586 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233157AbiGLROo (ORCPT ); Tue, 12 Jul 2022 13:14:44 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 99B52B7D40 for ; Tue, 12 Jul 2022 10:14:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657646082; 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=6LWoZxmGBMuZPprfyc1QWNTPJ/dMjvswUT54ENVWGNc=; b=U9fGUvKs97xBWLjQfLDdaeWOoFTcNmqDEh3qMCm1o1RiXpmAUNwCi12uPC+R8+3D2iDdJ+ jllSQCY/wgj1N6cly1JOZDwrwzn1rJktSRBbnuBrRuiVb3LagRjZdWnz4ZAzdkpBg0OYX1 VAxD8tictNoIA6RBlmJHWdABUL4WAS4= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-536-C_ZyTGIwMLqpAZaC5gEHpA-1; Tue, 12 Jul 2022 13:14:35 -0400 X-MC-Unique: C_ZyTGIwMLqpAZaC5gEHpA-1 Received: by mail-wm1-f70.google.com with SMTP id v18-20020a05600c15d200b003a2d4809386so6961949wmf.4 for ; Tue, 12 Jul 2022 10:14:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:to:cc :references:subject:content-language:from:in-reply-to :content-transfer-encoding; bh=6LWoZxmGBMuZPprfyc1QWNTPJ/dMjvswUT54ENVWGNc=; b=MdaXJ/gHJygZ+8utYYmQNpFo3bVP6mg2IrygkWHkndHFTuBZ/fm0hn6hI/q5VlF3Am LPWjWN7z6tn8whXkrE4eHrG2UIFYKrOzoGHsH76BJZRc/fE93NEtv+GL+3mTCrzCfdFP M7LzqLvGY7/+INrOn2L8w/6VjvvZwL8MnwfWi/KmLk22u/g4xRrP5AdaAxTGEIjQbbZS K86KirZTXjoatdHk/jfT8ZIIYFLRMw62DmE+GDgHRF3q7dlkmzs1YeXwr0dRIeHBovAq zf1oI+wniAL8IEGZTDSOMWnMAfDGV4sPeQMWoNdgsbgRfESeUQNAcEN2rEupZqyFg7fy KAyg== X-Gm-Message-State: AJIora8+hE//BxWJYlg0Yyhaei8/vR2KHZ0+0sIvWtg+jjYL5IDjT40j tyNQl4zU18Na+czjZHqWXG5j8gAY5jpTgtf34k1sqV7x84uY76naR79w4zR/YCCyyDRq9OYB5fz ff2zbbbZFW3AmRF9I/pE= X-Received: by 2002:a5d:6d0e:0:b0:21d:6d4c:e0e4 with SMTP id e14-20020a5d6d0e000000b0021d6d4ce0e4mr24192065wrq.355.1657646074535; Tue, 12 Jul 2022 10:14:34 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v2F0cZX1TI83MjeQF5zCeIy2jw6sxxjhgQt61Lv57WOfETN0CAXdHA7iZyl7plmECX4COjcA== X-Received: by 2002:a5d:6d0e:0:b0:21d:6d4c:e0e4 with SMTP id e14-20020a5d6d0e000000b0021d6d4ce0e4mr24192032wrq.355.1657646074266; Tue, 12 Jul 2022 10:14:34 -0700 (PDT) Received: from [192.168.9.27] (net-2-34-30-100.cust.vodafonedsl.it. [2.34.30.100]) by smtp.gmail.com with ESMTPSA id n6-20020adfe786000000b0021b9504cc83sm8788767wrm.31.2022.07.12.10.14.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Jul 2022 10:14:33 -0700 (PDT) Message-ID: <1aec7d55-24d5-e9bc-9052-728335ec7d9d@redhat.com> Date: Tue, 12 Jul 2022 19:14:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 To: matthew.gerlach@linux.intel.com Cc: basheer.ahmed.muddebihal@intel.com, corbet@lwn.net, hao.wu@intel.com, linux-doc@vger.kernel.org, linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org, mdf@kernel.org, russell.h.weight@intel.com, tianfei.zhang@intel.com, trix@redhat.com, yilun.xu@intel.com References: <20220707150549.265621-2-matthew.gerlach@linux.intel.com> Subject: Re: [PATCH v3 1/2] Documentation: fpga: dfl: add PCI Identification documentation Content-Language: en-US From: Marco Pagani In-Reply-To: <20220707150549.265621-2-matthew.gerlach@linux.intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 2022-07-07 17:05, matthew.gerlach@linux.intel.com wrote: > From: Matthew Gerlach > > Add documentation on identifying FPGA based PCI cards prompted > by discussion on the linux-fpga@vger.kernel.org mailing list. > > Signed-off-by: Matthew Gerlach > --- > v3: Add url to page tracking PCI ID information for DFL based cards. > > v2: Introduced in v2. > --- > Documentation/fpga/dfl.rst | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) > > diff --git a/Documentation/fpga/dfl.rst b/Documentation/fpga/dfl.rst > index 15b670926084..5144775b860a 100644 > --- a/Documentation/fpga/dfl.rst > +++ b/Documentation/fpga/dfl.rst > @@ -507,6 +507,27 @@ ids application. > https://github.com/OPAE/dfl-feature-id > > > +PCI Device Identification > +================================ > +Since FPGA based PCI cards can be reconfigured to a perform a completely There's a small typo: "to a perform" --> "to perform" > +new function at runtime, properly identifying such cards and binding the > +correct driver can be challenging. In many use cases, deployed FPGA based > +PCI cards are essentially static and the PCI Product ID and Vendor ID pair > +is sufficient to identify the card. The DFL framework helps with the > +dynamic case of deployed FPGA cards changing at run time by providing > +more detailed information about card discoverable at runtime. > + > +At one level, the DFL on a PCI card describes the function of the card. > +However, the same DFL could be instantiated on different physical cards. > +Conversely, different DFLs could be instantiated on the same physical card. > +Practical management of a cloud containing a heterogeneous set of such cards > +requires a PCI level of card identification. While the PCI Product ID and > +Vendor ID may be sufficient to bind the dfl-pci driver, it is expected > +that FPGA PCI cards would advertise suitable Subsystem ID and Subsystem > +Vendor ID values. Further PCI Product, Vendor, and Subsystem id tracking > +can be found at https://github.com/OPAE/dfl-feature-id/blob/main/dfl-pci-ids.rst. > + > + > Location of DFLs on a PCI Device > ================================ > The original method for finding a DFL on a PCI device assumed the start of the Marco