Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp127582pxm; Tue, 22 Feb 2022 18:37:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJydsOZ9wk3oZjzE4rM69vULo4j93NlMbr83zTez7yGrva8dGh4BmZRjEkGqCUQ8g8Dxwd68 X-Received: by 2002:a17:90b:364f:b0:1bc:7337:d7df with SMTP id nh15-20020a17090b364f00b001bc7337d7dfmr5905165pjb.61.1645583847071; Tue, 22 Feb 2022 18:37:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645583847; cv=none; d=google.com; s=arc-20160816; b=krBqNaseD5C8/4RjfE3VuWUFHFOb+ylQLZutcTN+Yb8QPIn1c/43ni+BXyjKUPDAz1 2yxqbjC/jNBMu+vSETg9e5VOfgeZCuPV+i3Ao6LKSfV6KW5qNnnkMEJtbM9oGdwNsQEG 3oYVL30vhjFhtEmrh1R8Bxr7g2Lq7gLEFCrSAR0T4ZH6v143Nur56rASkdtB6dCkvlBn fb6knnx6S+Ya9DL/L4ZGxHfD1YOFWqDVYUgtvkkPEvn7Lri3oA2CVKJWu2vwqBruJi54 CP1uP3PMfa5eXEQKAVjp42Id4q1pAJJfJBzSr1vBJbVwbp8lIFqu7jRGim5alH8ZYfq6 HyzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=Q/F/MVRVsTXPiEmPkOpNXGwvpePHO5WGa1Rhgl2MILM=; b=Ja9tmeJOOOj3KyQrv7cU95N5jOTHB0w7Lv+G1azGuZONtB2nmnm9DH38zcSHXbaz1m cZPuqdkhTlm7azla40YpTfITMPzcw0Dmx8hSGuBOD7OxoOWytTY21sgQfoJhVa3MGa/7 2v9a8IE2iZz45B4jiaWMvw0XKrT5C8Oz+76Cfjuk+TYuRiwC3DiyEqt2Xk2SabQQ+lvr UE1QcWYuquoZeGcejlfGGRuOdiwaskra5O/wZVBl6Iz3f044JEzozbBVOF3gelMhpyDY rntjhkq9FdxcFDuD+aPbENcUDyGSYrGrSqfvuYOLQCPdyRGNoUqmjo2WNZq9DvQOnwzj /bNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cprzcBtk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s193si21585154pgs.318.2022.02.22.18.37.11; Tue, 22 Feb 2022 18:37:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=cprzcBtk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S233894AbiBVQLw (ORCPT + 99 others); Tue, 22 Feb 2022 11:11:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37848 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231902AbiBVQLu (ORCPT ); Tue, 22 Feb 2022 11:11:50 -0500 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 B6ABD165C22 for ; Tue, 22 Feb 2022 08:11:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1645546283; 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=Q/F/MVRVsTXPiEmPkOpNXGwvpePHO5WGa1Rhgl2MILM=; b=cprzcBtknGzdxpAU5mh3BxRFgjAnKpWlnOhHfbH6cyYIip2Il0Hjb+banUnY9U53foVKPT MBxrfcsR3kz76SsSdO15nXGdBGFFSAJnaOY/vWQ12VkNwMByowOlx01tzn9LCfYS3WDL0u j30x7RNJv/XHmbk90w4t7ndnJGSHg58= Received: from mail-qv1-f72.google.com (mail-qv1-f72.google.com [209.85.219.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-168-R7ilihyANcCm1yO2TKnz3A-1; Tue, 22 Feb 2022 11:11:22 -0500 X-MC-Unique: R7ilihyANcCm1yO2TKnz3A-1 Received: by mail-qv1-f72.google.com with SMTP id kd18-20020a056214401200b0042de5c14702so14146qvb.12 for ; Tue, 22 Feb 2022 08:11:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Q/F/MVRVsTXPiEmPkOpNXGwvpePHO5WGa1Rhgl2MILM=; b=UDmyxUcAfhVXB2b0GCt/SK8OHfOxzyhzGiruLHo037QFZ2uaNPomV/t25YJlVM08rb JPLbR/7aWyASFtolLvVgPCrxkSktdlM4VxAFzEMqNtTzo5bydQaasCGfjocCsRoDKf2H Z0XECOVFNm3XgWHUbWFxwbgMRo6vfl0rl8CL7gU9f6l6pBDQENu8fv5tm3xTJyQuo8qB mf+IHCbhwNc6N1RH/IKb8pWwc76zSrK9HN9IxUqh+4W49cTQ/r6fIAwu6RToNgA+TaCY v9lYxASDujX6bOfL6B8pNTo2HbK7qKUVl/jJcgFweST30vR3rS8ilXyRCRFVVuWlrYzm ZzCA== X-Gm-Message-State: AOAM530GFFom2WRkc9ektV/BvuKGBsqjxHxMu86KY/t5Jm1L9L0mBcH6 cy6JPI4D5qHIo48hRhclPOTnI8ouxE5D26D4lEK1Uu/j2ag4oTvimevZZb3n0losjFBKjYNitey 3CU2qL6Gmhd9WaY1XwA7pxOhK X-Received: by 2002:a05:622a:1742:b0:2de:15f5:3174 with SMTP id l2-20020a05622a174200b002de15f53174mr9829651qtk.120.1645546281609; Tue, 22 Feb 2022 08:11:21 -0800 (PST) X-Received: by 2002:a05:622a:1742:b0:2de:15f5:3174 with SMTP id l2-20020a05622a174200b002de15f53174mr9829629qtk.120.1645546281336; Tue, 22 Feb 2022 08:11:21 -0800 (PST) Received: from localhost.localdomain (024-205-208-113.res.spectrum.com. [24.205.208.113]) by smtp.gmail.com with ESMTPSA id r3sm14288qkm.56.2022.02.22.08.11.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 22 Feb 2022 08:11:20 -0800 (PST) Subject: Re: [PATCH v1 7/7] fpga: dfl: pci: Add generic OFS PCI PID To: "Zhang, Tianfei" , "matthew.gerlach@linux.intel.com" Cc: "Wu, Hao" , "mdf@kernel.org" , "Xu, Yilun" , "linux-fpga@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "corbet@lwn.net" References: <20220214112619.219761-1-tianfei.zhang@intel.com> <20220214112619.219761-8-tianfei.zhang@intel.com> <3c9fce03-ef29-d80f-6639-0c237c28cf58@redhat.com> From: Tom Rix Message-ID: Date: Tue, 22 Feb 2022 08:11:18 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/21/22 7:11 PM, Zhang, Tianfei wrote: > >> -----Original Message----- >> From: Tom Rix >> Sent: Tuesday, February 22, 2022 2:10 AM >> To: matthew.gerlach@linux.intel.com >> Cc: Zhang, Tianfei ; Wu, Hao ; >> mdf@kernel.org; Xu, Yilun ; linux-fpga@vger.kernel.org; >> linux-doc@vger.kernel.org; linux-kernel@vger.kernel.org; corbet@lwn.net >> Subject: Re: [PATCH v1 7/7] fpga: dfl: pci: Add generic OFS PCI PID >> >> >> On 2/21/22 9:50 AM, matthew.gerlach@linux.intel.com wrote: >>> >>> On Fri, 18 Feb 2022, Tom Rix wrote: >>> >>>> On 2/18/22 1:03 AM, Zhang, Tianfei wrote: >>>>>> -----Original Message----- >>>>>> From: Tom Rix >>>>>> Sent: Wednesday, February 16, 2022 12:16 AM >>>>>> To: Zhang, Tianfei ; Wu, Hao >>>>>> ; mdf@kernel.org; Xu, Yilun ; >>>>>> linux-fpga@vger.kernel.org; linux-doc@vger.kernel.org; >>>>>> linux-kernel@vger.kernel.org >>>>>> Cc: corbet@lwn.net; Matthew Gerlach >>>>>> >>>>>> Subject: Re: [PATCH v1 7/7] fpga: dfl: pci: Add generic OFS PCI PID >>>>>> >>>>>> >>>>>> On 2/14/22 3:26 AM, Tianfei zhang wrote: >>>>>>> From: Matthew Gerlach >>>>>>> >>>>>>> Add the PCI product id for an Open FPGA Stack PCI card. >>>>>> Is there a URL to the card ? >>>>> This PCIe Device IDs have registered by Intel. >>>> A URL is useful to introduce the board, Is there one ? >>>>>>> Signed-off-by: Matthew Gerlach >>>>>>> Signed-off-by: Tianfei Zhang >>>>>>> --- >>>>>>>    drivers/fpga/dfl-pci.c | 4 ++++ >>>>>>>    1 file changed, 4 insertions(+) >>>>>>> >>>>>>> diff --git a/drivers/fpga/dfl-pci.c b/drivers/fpga/dfl-pci.c index >>>>>>> 83b604d6dbe6..cb2fbf3eb918 100644 >>>>>>> --- a/drivers/fpga/dfl-pci.c >>>>>>> +++ b/drivers/fpga/dfl-pci.c >>>>>>> @@ -76,12 +76,14 @@ static void cci_pci_free_irq(struct pci_dev >>>>>>> *pcidev) >>>>>>>    #define PCIE_DEVICE_ID_INTEL_PAC_D5005        0x0B2B >>>>>>>    #define PCIE_DEVICE_ID_SILICOM_PAC_N5010    0x1000 >>>>>>>    #define PCIE_DEVICE_ID_SILICOM_PAC_N5011    0x1001 >>>>>>> +#define PCIE_DEVICE_ID_INTEL_OFS        0xbcce >>>>>> INTEL_OFS is a generic name, pci id's map to specific cards >>>>>> >>>>>> Is there a more specific name for this card ? >>>>> I think using INTEL_OFS is better, because INTEL_OFS is the Generic >>>>> development platform can support multiple cards which using OFS >>>>> specification, like Intel PAC N6000 card. >>>> I would prefer something like PCIE_DEVICE_ID_INTEL_PAC_N6000 because >>>> it follows an existing pattern.  Make it easy on a developer, they >>>> will look at their board or box, see X and try to find something >>>> similar in the driver source. >>>> >>>> To use OSF_ * the name needs a suffix to differentiate it from future >>>> cards that will also use ofs. >>>> >>>> If this really is a generic id please explain in the doc patch how >>>> every future board with use this single id and how a driver could >>>> work around a hw problem in a specific board with a pci id covering >>>> multiple boards. >>>> >>>> Tom >>> Hi Tom, >>> >>> The intent is to have a generic device id that can be used with many >>> different boards.  Currently, we have FPGA implementations for 3 >>> different boards using this generic id.  We may need a better name for >>> device id than OFS.  More precisely this generic device id means a PCI >>> function that is described by a Device Feature List (DFL).  How about >>> PCIE_DEVICE_ID_INTEL_DFL? >>> >>> With a DFL device id, the functionality of the PF/VF is determined by >>> the contents of the DFL.  Each Device Feature Header (DFH) in the DFL >>> has a revision field that can be used identify "broken" hw, or new >>> functionality added to a feature.  Additionally, since the DFL is >>> typically used in a FPGA, the broken hardware, can and should be fixed >>> in most cases. >> How is lspci supposed to work ? > There is an example for one card using IOFS and DFL. > > # lspci | grep acc > b1:00.0 Processing accelerators: Intel Corporation Device bcce (rev 01) > b1:00.1 Processing accelerators: Intel Corporation Device bcce > b1:00.2 Processing accelerators: Intel Corporation Device bcce > b1:00.3 Processing accelerators: Red Hat, Inc. Virtio network device > b1:00.4 Processing accelerators: Intel Corporation Device bcce > > Note: There 5 PFs in this card, it exports the management functions via PF0(b1:00.0), > Other PFs like b1:00.1, b1:00.2, b1:00.4, are using for testing, which depends on RTL designer > or project requirement. The PF3 instance a VirtIO net device for example, will bind with virtio-net driver > presenting itself as a network interface to the OS. What I mean there is heterogeneous set of cards in one machine, how do you tell which card is which ? Or in a datacenter where the machines are all remote and admin has to flash just the n6000's ? How could she find just the n6000's with lspci ? How would the driver know ? Tom > >> A dfl set can change with fw updates and in theory different boards could have >> the same set. >> >> Tom >> >>> Matthew >>>>>> Tom >>>>>> >>>>>>>    /* VF Device */ >>>>>>>    #define PCIE_DEVICE_ID_VF_INT_5_X        0xBCBF >>>>>>>    #define PCIE_DEVICE_ID_VF_INT_6_X        0xBCC1 >>>>>>>    #define PCIE_DEVICE_ID_VF_DSC_1_X        0x09C5 >>>>>>>    #define PCIE_DEVICE_ID_INTEL_PAC_D5005_VF    0x0B2C >>>>>>> +#define PCIE_DEVICE_ID_INTEL_OFS_VF        0xbccf >>>>>>> >>>>>>>    static struct pci_device_id cci_pcie_id_tbl[] = { >>>>>>>        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, >>>>>>> PCIE_DEVICE_ID_PF_INT_5_X),}, >>>>>> @@ >>>>>>> -95,6 +97,8 @@ static struct pci_device_id cci_pcie_id_tbl[] = { >>>>>>>        {PCI_DEVICE(PCI_VENDOR_ID_INTEL, >>>>>> PCIE_DEVICE_ID_INTEL_PAC_D5005_VF),}, >>>>>>> {PCI_DEVICE(PCI_VENDOR_ID_SILICOM_DENMARK, >>>>>> PCIE_DEVICE_ID_SILICOM_PAC_N5010),}, >>>>>>> {PCI_DEVICE(PCI_VENDOR_ID_SILICOM_DENMARK, >>>>>>> PCIE_DEVICE_ID_SILICOM_PAC_N5011),}, >>>>>>> +    {PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCIE_DEVICE_ID_INTEL_OFS),}, >>>>>>> +    {PCI_DEVICE(PCI_VENDOR_ID_INTEL, >>>>>> PCIE_DEVICE_ID_INTEL_OFS_VF),}, >>>>>>>        {0,} >>>>>>>    }; >>>>>>>    MODULE_DEVICE_TABLE(pci, cci_pcie_id_tbl); >>>>