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 09/11] vpci/rebar: Remove registers when init_rebar() fails
Date: Thu, 8 May 2025 11:39:01 +0200 [thread overview]
Message-ID: <aBx7teQ9ZoI0s4Jt@macbook.lan> (raw)
In-Reply-To: <20250421061903.1542652-10-Jiqian.Chen@amd.com>
On Mon, Apr 21, 2025 at 02:19:01PM +0800, Jiqian Chen wrote:
> When init_rebar() fails, the previous new changes will hide Rebar
> capability, it can't rely on vpci_deassign_device() to remove all
> Rebar related registers anymore, those registers must be removed
> fini_rebar().
>
> To do that, call vpci_remove_registers() to remove all possible
> registered registers.
>
> Signed-off-by: Jiqian Chen <Jiqian.Chen@amd.com>
> ---
> cc: "Roger Pau Monné" <roger.pau@citrix.com>
> ---
> v2->v3 changes:
> * Use fini_rebar() to remove all register instead of in the failure path of init_rebar();
>
> v1->v2 changes:
> * Called vpci_remove_registers() to remove all possible registered registers instead of using a array to record all registered register.
>
> Best regards,
> Jiqian Chen.
> ---
> xen/drivers/vpci/rebar.c | 35 ++++++++++++++++++++++++-----------
> 1 file changed, 24 insertions(+), 11 deletions(-)
>
> diff --git a/xen/drivers/vpci/rebar.c b/xen/drivers/vpci/rebar.c
> index 026f8f7972d9..325090afb0f8 100644
> --- a/xen/drivers/vpci/rebar.c
> +++ b/xen/drivers/vpci/rebar.c
> @@ -49,6 +49,26 @@ static void cf_check rebar_ctrl_write(const struct pci_dev *pdev,
> bar->guest_addr = bar->addr;
> }
>
> +static void fini_rebar(struct pci_dev *pdev)
> +{
> + uint32_t ctrl;
> + unsigned int nbars;
> + unsigned int rebar_offset = pci_find_ext_capability(pdev->sbdf,
> + PCI_EXT_CAP_ID_REBAR);
> +
> + if ( !rebar_offset || !is_hardware_domain(pdev->domain) )
Maybe add an ASSERT_UNREACHABLE() here? I don't think we are expected
to get into the cleanup function for the capability if it's not
present, or if the owner of the device is not the hardware domain.
> + return;
> +
> + ctrl = pci_conf_read32(pdev->sbdf, rebar_offset + PCI_REBAR_CTRL(0));
> + nbars = MASK_EXTR(ctrl, PCI_REBAR_CTRL_NBAR_MASK);
> + /*
> + * Remove all possible registered registers except header.
> + * Header register will be removed in mask function.
> + */
> + vpci_remove_registers(pdev->vpci, rebar_offset + PCI_REBAR_CAP(0),
> + PCI_REBAR_CTRL(nbars - 1));
> +}
> +
> static int cf_check init_rebar(struct pci_dev *pdev)
> {
> uint32_t ctrl;
> @@ -80,7 +100,7 @@ static int cf_check init_rebar(struct pci_dev *pdev)
> {
> printk(XENLOG_ERR "%pd %pp: too big BAR number %u in REBAR_CTRL\n",
> pdev->domain, &pdev->sbdf, index);
> - continue;
> + return -EINVAL;
-E2BIG might be better here. In general I try to avoid using EINVAL,
as it's a catch all that makes differentiating error later on harder.
> }
>
> bar = &pdev->vpci->header.bars[index];
> @@ -88,7 +108,7 @@ static int cf_check init_rebar(struct pci_dev *pdev)
> {
> printk(XENLOG_ERR "%pd %pp: BAR%u is not in memory space\n",
> pdev->domain, &pdev->sbdf, index);
> - continue;
> + return -EINVAL;
Maybe -EDOM here? -ENXIO or EIO might also be appropriate.
Overall looks good.
Thanks, Roger.
next prev parent reply other threads:[~2025-05-08 9:39 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é
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é [this message]
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=aBx7teQ9ZoI0s4Jt@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.