All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jiqian Chen <Jiqian.Chen@amd.com>
Cc: xen-devel@lists.xenproject.org, Huang Rui <ray.huang@amd.com>
Subject: Re: [PATCH v3 04/11] vpci/header: Emulate extended capability list for dom0
Date: Tue, 6 May 2025 16:14:30 +0200	[thread overview]
Message-ID: <aBoZRicr20a4eCNV@macbook.lan> (raw)
In-Reply-To: <20250421061903.1542652-5-Jiqian.Chen@amd.com>

On Mon, Apr 21, 2025 at 02:18:56PM +0800, Jiqian Chen wrote:
> Add a new function to emulate extended capability list for dom0,
> and call it in init_header(). So that it will be easy to hide a
> extended capability whose initialization fails.
> 
> As for the extended capability list of domU, just move the logic
> into above function and keep hiding it for domU.
> 
> Signed-off-by: Jiqian Chen <Jiqian.Chen@amd.com>
> ---
> cc: "Roger Pau Monné" <roger.pau@citrix.com>
> ---
> v2->v3 changes:
> * In vpci_init_ext_capability_list(), when domain is domU, directly return after adding a handler(hiding all extended capability for domU).
> * In vpci_init_ext_capability_list(), change condition to be "while ( pos >= 0x100U && ttl-- )" instead of "while ( pos && ttl-- )".
> * Add new function vpci_hw_write32, and pass it to extended capability handler for dom0.
> 
> v1->v2 changes:
> new patch
> 
> Best regards,
> Jiqian Chen.
> ---
>  xen/drivers/vpci/header.c | 36 ++++++++++++++++++++++++++++--------
>  xen/drivers/vpci/vpci.c   |  6 ++++++
>  xen/include/xen/vpci.h    |  2 ++
>  3 files changed, 36 insertions(+), 8 deletions(-)
> 
> diff --git a/xen/drivers/vpci/header.c b/xen/drivers/vpci/header.c
> index c98cd211d9d7..ee94ad8e5037 100644
> --- a/xen/drivers/vpci/header.c
> +++ b/xen/drivers/vpci/header.c
> @@ -817,6 +817,31 @@ static int vpci_init_capability_list(struct pci_dev *pdev)
>                                    PCI_STATUS_RSVDZ_MASK);
>  }
>  
> +static int vpci_init_ext_capability_list(struct pci_dev *pdev)
> +{
> +    unsigned int pos = PCI_CFG_SPACE_SIZE, ttl = 480;
> +
> +    if ( !is_hardware_domain(pdev->domain) )
> +        /* Extended capabilities read as zero, write ignore for guest */
> +        return vpci_add_register(pdev->vpci, vpci_read_val, NULL,
> +                                 pos, 4, (void *)0);
> +
> +    while ( pos >= PCI_CFG_SPACE_SIZE && ttl-- )
> +    {
> +        uint32_t header = pci_conf_read32(pdev->sbdf, pos);
> +        int rc;

I'm thinking it might be helpful to avoid setting the handler for the
last capability on the list, or simply for devices that have no
extended capabilities at all:

if ( PCI_EXT_CAP_NEXT(header) >= PCI_CFG_SPACE_SIZE )
{
    int rc = vpci_add_register(pdev->vpci, vpci_read_val, vpci_hw_write32,
                               pos, 4, (void *)(uintptr_t)header);

    if ( rc )
        return rc;
}

Otherwise on systems with a lot of devices it can be quite wasteful to
set a handler to just return the next capability as 0.

Thanks, Roger.


  reply	other threads:[~2025-05-06 14:14 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21  6:18 [PATCH v3 00/11] Support hiding capability when its initialization fails Jiqian Chen
2025-04-21  6:18 ` [PATCH v3 01/11] vpci/header: Move emulating cap list logic into new function Jiqian Chen
2025-04-29  7:10   ` Chen, Jiqian
2025-05-06 13:30   ` Roger Pau Monné
2025-04-21  6:18 ` [PATCH v3 02/11] driver/pci: Get next capability without passing caps Jiqian Chen
2025-04-22 15:59   ` Jan Beulich
2025-04-23  3:13     ` Chen, Jiqian
2025-04-21  6:18 ` [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0 Jiqian Chen
2025-04-22 16:01   ` Jan Beulich
2025-04-23  3:31     ` Chen, Jiqian
2025-04-23  7:27       ` Jan Beulich
2025-05-06 13:47   ` Roger Pau Monné
2025-05-06 13:50   ` Roger Pau Monné
2025-05-07  2:46     ` Chen, Jiqian
2025-05-07  2:50       ` Chen, Jiqian
2025-05-07  7:49       ` Roger Pau Monné
2025-05-07  8:13         ` Chen, Jiqian
2025-04-21  6:18 ` [PATCH v3 04/11] vpci/header: Emulate extended " Jiqian Chen
2025-05-06 14:14   ` Roger Pau Monné [this message]
2025-05-07  3:32     ` Chen, Jiqian
2025-05-07  7:55       ` Roger Pau Monné
2025-04-21  6:18 ` [PATCH v3 05/11] vpci: Refactor REGISTER_VPCI_INIT Jiqian Chen
2025-04-22 16:03   ` Jan Beulich
2025-04-23  3:49     ` Chen, Jiqian
2025-04-23  7:36       ` Jan Beulich
2025-04-23  8:17         ` Chen, Jiqian
2025-05-06 14:37   ` Roger Pau Monné
2025-05-07  5:59     ` Chen, Jiqian
2025-05-07  8:04       ` Roger Pau Monné
2025-05-07  8:23         ` Chen, Jiqian
2025-04-21  6:18 ` [PATCH v3 06/11] vpci: Hide legacy capability when it fails to initialize Jiqian Chen
2025-05-06 16:00   ` Roger Pau Monné
2025-05-07  6:38     ` Chen, Jiqian
2025-05-07  8:07       ` Roger Pau Monné
2025-04-21  6:18 ` [PATCH v3 07/11] vpci: Hide extended " Jiqian Chen
2025-04-22 16:06   ` Jan Beulich
2025-05-08  9:16     ` Chen, Jiqian
2025-05-08  9:47       ` Roger Pau Monné
2025-05-06 16:21   ` Roger Pau Monné
2025-05-07  7:26     ` Chen, Jiqian
2025-05-07  8:09       ` Roger Pau Monné
2025-05-07  8:49         ` Chen, Jiqian
2025-05-07  9:05           ` Roger Pau Monné
2025-04-21  6:19 ` [PATCH v3 08/11] vpci: Refactor vpci_remove_register to remove matched registers Jiqian Chen
2025-05-06 16:29   ` Roger Pau Monné
2025-04-21  6:19 ` [PATCH v3 09/11] vpci/rebar: Remove registers when init_rebar() fails Jiqian Chen
2025-05-08  9:39   ` Roger Pau Monné
2025-05-09  5:27     ` Chen, Jiqian
2025-04-21  6:19 ` [PATCH v3 10/11] vpci/msi: Free MSI resources when init_msi() fails Jiqian Chen
2025-05-08  9:57   ` Roger Pau Monné
2025-04-21  6:19 ` [PATCH v3 11/11] vpci/msix: Add function to clean MSIX resources Jiqian Chen
2025-05-08 10:04   ` Roger Pau Monné
2025-05-09  5:45     ` Chen, Jiqian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aBoZRicr20a4eCNV@macbook.lan \
    --to=roger.pau@citrix.com \
    --cc=Jiqian.Chen@amd.com \
    --cc=ray.huang@amd.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.