Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp2220975pxb; Fri, 25 Mar 2022 13:18:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9IY/jhmtML60ifBR2BWHkRYoDYk+XaPRAL++nleS6dMyRk7+OridpaCWbiLVJD0Z2J7I0 X-Received: by 2002:a17:90b:4b89:b0:1c7:d452:4bc1 with SMTP id lr9-20020a17090b4b8900b001c7d4524bc1mr9200862pjb.134.1648239526478; Fri, 25 Mar 2022 13:18:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648239526; cv=none; d=google.com; s=arc-20160816; b=SX07FgSwq/iLq20+Tg7T2HeucrKtobj6kUwYBtcQdTX+pI5B7n+yP9ztIGlCcdGx/g v+iPRriHA1JswIxqRd3+JyshkyHy+zKr3QyXt1iIMw9l1O+r4xCuGPrmC+4ZmcANYZor TwkGsUWcKXCOUL29xO/yuCoY+r5pZ8VwcQ6EMapiLnSxfVQ7H02vzEcuc5PX2l40IjGb 5snKAXj4DfJQs0rT0JXfdpV8us1kBYB5oSb0nt7z5hpUZbMXa3RbLIHWrrp4qOjEFqyv BJAw4X5PKwjPjdhizK3ZWnR5V2YFJ/H0lSEnV/zJWTI6JidzXSvdDJ/TtSY7bNaaUNak 8Fog== 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 :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=/vpt4aozEDlYTo5SA/UumAmv//ASZGWZG7LLYxpYnnI=; b=SC6OTHOsCTsWaLzO7nrnglwOQackMI1YW9PLozbuwqf2WmOpCrNIwOIhIJo+U+72xJ XEohSWiGo0tHtDrrfNe8qDJfowZeRj/2Tfi22nmNrgXaj3Pn6YLHHtGndLL7IH7bAhXO qXLQyaUvtHY/5QFzQSI9FDjcm2k/9OQjrcXjd0PGO/FGPgrcmiZaYoYyDBURjf7qheJu T3bY9aYPOwHPVdzcz8rEiqv+hBFqA+sIq+WXLFmSms89H0fj6e3QeHDJBf2zKC07IJQl HSrcj1Col/ztlg0/fUQCLZq39sz9HdY2Ksnr1sm3B0RIwrx8/G//g83NBXpyYLVPST/S u1OQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id l4-20020a17090aec0400b001c6e2da4524si3302689pjy.183.2022.03.25.13.18.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Mar 2022 13:18:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 290313C64F6; Fri, 25 Mar 2022 12:16:38 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1358215AbiCYMEc (ORCPT + 99 others); Fri, 25 Mar 2022 08:04:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358082AbiCYMEa (ORCPT ); Fri, 25 Mar 2022 08:04:30 -0400 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94F01D4C93; Fri, 25 Mar 2022 05:02:55 -0700 (PDT) Received: from fraeml742-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KQ0zl44lXz6864S; Fri, 25 Mar 2022 20:01:07 +0800 (CST) Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by fraeml742-chm.china.huawei.com (10.206.15.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Fri, 25 Mar 2022 13:02:53 +0100 Received: from localhost (10.47.31.18) by lhreml710-chm.china.huawei.com (10.201.108.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Fri, 25 Mar 2022 12:02:52 +0000 Date: Fri, 25 Mar 2022 12:02:46 +0000 From: Jonathan Cameron To: Ira Weiny CC: Bjorn Helgaas , Dan Williams , Bjorn Helgaas , "Alison Schofield" , Vishal Verma , Ben Widawsky , , , Subject: Re: [PATCH V6 04/10] PCI/DOE: Introduce pci_doe_create_doe_devices Message-ID: <20220325120246.000028de@Huawei.com> In-Reply-To: References: <20220201071952.900068-5-ira.weiny@intel.com> <20220203224437.GA120552@bhelgaas> <20220324140539.00004be8@Huawei.com> Organization: Huawei Technologies Research and Development (UK) Ltd. X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.29; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.47.31.18] X-ClientProxiedBy: lhreml753-chm.china.huawei.com (10.201.108.203) To lhreml710-chm.china.huawei.com (10.201.108.61) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Thu, 24 Mar 2022 16:44:33 -0700 Ira Weiny wrote: > On Thu, Mar 24, 2022 at 02:05:39PM +0000, Jonathan Cameron wrote: > > Hi Ira, > > > > > Here is the code to be more clear... > > > > > > > > > drivers/cxl/pci.c: > > > > > > int cxl_pci_create_doe_devices(struct pci_dev *pdev) > > > { > > > struct device *dev = &pdev->dev; > > > bool use_irq = true; > > > int irqs = 0; > > > u16 off = 0; > > > int rc; > > > > > > pci_doe_for_each_off(pdev, off) > > > irqs++; > > > pci_info(pdev, "Found %d DOE mailbox's\n", irqs); > > > > > > /* > > > * Allocate enough vectors for the DOE's > > > */ > > > rc = pci_alloc_irq_vectors(pdev, irqs, irqs, PCI_IRQ_MSI | > > > PCI_IRQ_MSIX); > > > if (rc != irqs) { > > > pci_err(pdev, "Not enough interrupts for all the DOEs; use polling\n"); > > > use_irq = false; > > > /* Some got allocated; clean them up */ > > > if (rc > 0) > > > cxl_pci_free_irq_vectors(pdev); > > > } else { > > > /* > > > * Enabling bus mastering is require for MSI/MSIx. It could be > > > * done later within the DOE initialization, but as it > > > * potentially has other impacts keep it here when setting up > > > * the IRQ's. > > > */ > > > pci_set_master(pdev); > > > rc = devm_add_action_or_reset(dev, > > > cxl_pci_free_irq_vectors, > > > pdev); > > > if (rc) > > > return rc; > > > } > > > > > > pci_doe_for_each_off(pdev, off) { > > > ... > > > /* Create each auxiliary device which internally calls */ > > > pci_doe_create_mb(pdev, off, use_irq); > > > ... > > > } > > > ... > > > } > > > > > > > > > drivers/pci/pci-doe.c: > > > > > > static irqreturn_t pci_doe_irq_handler(int irq, void *data) > > > { > > > ... > > > } > > > > > > static int pci_doe_request_irq(struct pci_doe_mb *doe_mb) > > > { > > > struct pci_dev *pdev = doe_mb->pdev; > > > int offset = doe_mb->cap_offset; > > > int doe_irq, rc; > > > u32 val; > > > > > > pci_read_config_dword(pdev, offset + PCI_DOE_CAP, &val); > > > > > > if (!FIELD_GET(PCI_DOE_CAP_INT, val)) > > > return -ENOTSUPP; > > > > > > doe_irq = FIELD_GET(PCI_DOE_CAP_IRQ, val); > > > rc = pci_request_irq(pdev, doe_irq, pci_doe_irq_handler, > > > NULL, doe_mb, > > > "DOE[%d:%s]", doe_irq, pci_name(pdev)); > > > if (rc) > > > return rc; > > > > > > doe_mb->irq = doe_irq; > > > pci_write_config_dword(pdev, offset + PCI_DOE_CTRL, > > > PCI_DOE_CTRL_INT_EN); > > > return 0; > > > } > > > > > > struct pci_doe_mb *pci_doe_create_mb(struct pci_dev *pdev, u16 cap_offset, > > > bool use_irq) > > > { > > > ... > > > if (use_irq) { > > > rc = pci_doe_request_irq(doe_mb); > > > if (rc) > > > pci_err(pdev, "DOE request irq failed for mailbox @ %u : %d\n", > > > cap_offset, rc); > > > } > > > ... > > > } > > > > > > > > > Does this look reasonable? > > > > I'm a little nervous about how we are going to make DOEs on switches work. > > Guess I'll do an experiment once your next version is out and check we > > can do that reasonably cleanly. For switches we'll probably have to > > check for DOEs on all such ports and end up with infrastructure to > > map to all protocols we might see on a switch. > > Are the switches not represented as PCI devices in linux? > > If my vision of switches is correct I think that problem is independent of what > I'm solving here. In other words the relationship between a port on a switch > and a DOE capability on that switch will have to be established somehow and > nothing I'm doing precludes doing that, but at the same time nothing I'm doing > helps that either. Sure, I'm just expressing nervousness and would want a PoC of that at least to check it's not too nasty. The port drivers are rather 'unusual' in PCI so touching them always ends up more complex than I expect. Anyhow, start of cycle so should be plenty of time to do such an RFC once your code is out there. Jonathan > > Ira > > > > > Jonathan > > > > >