[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3] vpci: Add resizable bar support


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Chen, Jiqian" <Jiqian.Chen@xxxxxxx>
  • Date: Tue, 17 Dec 2024 08:22:28 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=gwVHidIimuTaiqlUBVJb3ndRK3bVXYzMoj55zuU/1UM=; b=FYVFbqsdPDZ2SBLb25d2+KWdua3ZjrBrGApdKB/OusHVvIME/t1or/bj5MfQaw8pG+8NUOc8p68E787zj4SDKrA853X+L/DisBjti06iThIPcjrefBDbSXtQIQat5yFIdjMbMY/BfXnEwGDxgJ95QU655HxJC8HccO0lBXB/zUt+2M10DsWHCHsQSZDh9LzlUINLBqaPwtIDJF0jHThAsy9Qdfd6C1JJ2VRg9sWr7/vFa4EGfCEjbqU4QI/LoBHR9Yyx2lg7vmwnvkMzcE+oqzJKA6KreXmW6QXh3VzLRK6IG1em+nUPnl+V+T4ysrxs7tCXs6GEadkmgRmVvOp74A==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=OEB6SryH+RncRkUaEnKjLLukZy/D/iOWnbCxmuIV0+eIRtw9hltf9sKX/FkEiPb5W82H+cLwTVQoq4asFFbLI/S/kzgEiBuuOlnzi2nEMnFdn08jlEaPJmOr/K6J2t1DBBCGp5oMUqvyQN1SrbW2mXN4RJ5Mg6iSpXIyXUwQWEdlM1xCzKnb90GpkGA7YSkCeNtBlSdUHeif259gdkLMs84Xv1A/Uea1Wmpw/6L0qcZ/8aAq2W+DH/1y0eOuSCW9K68Gmy9+nA8phBw+L4VF2Zl7Q+Rv13ZU5X+M6L+wW0lSv9qhONHYAWVceFvfVAF3I35/wkoLOWgnNPKLg5iVhg==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Cc: Roger Pau Monné <roger.pau@xxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, "Huang, Ray" <Ray.Huang@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "Chen, Jiqian" <Jiqian.Chen@xxxxxxx>
  • Delivery-date: Tue, 17 Dec 2024 08:22:36 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHbTSHk/+a4JH45i0iSPkOFUem08bLov7+AgAHlKwA=
  • Thread-topic: [PATCH v3] vpci: Add resizable bar support

On 2024/12/16 19:24, Jan Beulich wrote:
> On 13.12.2024 06:42, Jiqian Chen wrote:
>> --- /dev/null
>> +++ b/xen/drivers/vpci/rebar.c
>> @@ -0,0 +1,130 @@
>> +/* SPDX-License-Identifier: GPL-2.0-only */
>> +/*
>> + * Copyright (C) 2024 Advanced Micro Devices, Inc. All Rights Reserved.
>> + *
>> + * Author: Jiqian Chen <Jiqian.Chen@xxxxxxx>
>> + */
>> +
>> +#include <xen/hypercall.h>
>> +#include <xen/vpci.h>
>> +
>> +static void cf_check rebar_ctrl_write(const struct pci_dev *pdev,
>> +                                      unsigned int reg,
>> +                                      uint32_t val,
>> +                                      void *data)
>> +{
>> +    uint64_t size;
>> +    struct vpci_bar *bar = data;
>> +
>> +    size = PCI_REBAR_CTRL_SIZE(val);
>> +    if ( bar->enabled )
>> +    {
>> +        if ( size == bar->size )
>> +            return;
>> +
>> +        /*
>> +        * Refuse to resize a BAR while memory decoding is enabled, as
>> +        * otherwise the size of the mapped region in the p2m would become
>> +        * stale with the newly set BAR size, and the position of the BAR
>> +        * would be reset to undefined.  Note the PCIe specification also
>> +        * forbids resizing a BAR with memory decoding enabled.
>> +        */
>> +        gprintk(XENLOG_ERR,
>> +                "%pp: refuse to resize BAR with memory decoding enabled\n",
>> +                &pdev->sbdf);
>> +        return;
>> +    }
>> +
>> +    if ( !((size >> PCI_REBAR_SIZE_BIAS) &
>> +           MASK_EXTR(pci_conf_read32(pdev->sbdf,
>> +                                     reg - PCI_REBAR_CTRL + PCI_REBAR_CAP),
>> +                                     PCI_REBAR_CAP_SIZES)) )
>> +        gprintk(XENLOG_WARNING,
>> +                "%pp: new size %#lx is not supported by hardware\n",
>> +                &pdev->sbdf, size);
> 
> This only covers the 1Mb ... 128Tb range. What about the 256Tb ... 8Eb one?
Thank you for reminding me!
I will consider that in next version.

> 
>> +static int cf_check init_rebar(struct pci_dev *pdev)
>> +{
>> +    uint32_t ctrl;
>> +    unsigned int rebar_offset, nbars;
>> +
>> +    rebar_offset = pci_find_ext_capability(pdev->sbdf, 
>> PCI_EXT_CAP_ID_REBAR);
>> +
>> +    if ( !rebar_offset )
>> +        return 0;
>> +
>> +    if ( !is_hardware_domain(pdev->domain) )
>> +    {
>> +        printk("ReBar is not supported for domUs\n");
>> +        return -EOPNOTSUPP;
>> +    }
>> +
>> +    ctrl = pci_conf_read32(pdev->sbdf, rebar_offset + PCI_REBAR_CTRL);
>> +    nbars = MASK_EXTR(ctrl, PCI_REBAR_CTRL_NBAR_MASK);
>> +
>> +    for ( unsigned int i = 0; i < nbars; i++, rebar_offset += 
>> PCI_REBAR_CTRL )
> 
> PCI_REBAR_CTRL is an offset; it can't be used to bump rebar_offset here.
> That'll need a separate constant, even if both evaluate to 8.
I will add a new macro to represent the '8' in rebar.c
Maybe I can name it "PCI_REBAR_SINGLE_BAR_LEN" ?

> 
> Jan

-- 
Best regards,
Jiqian Chen.

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.