From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Chen, Jiqian" <Jiqian.Chen@amd.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Huang, Ray" <Ray.Huang@amd.com>
Subject: Re: [PATCH v5 08/10] vpci/rebar: Free Rebar resources when init_rebar() fails
Date: Fri, 6 Jun 2025 11:20:54 +0200 [thread overview]
Message-ID: <aEKy9nt8NNTKHaxo@macbook.local> (raw)
In-Reply-To: <BL1PR12MB5849F4955656B6D67D123E6EE76EA@BL1PR12MB5849.namprd12.prod.outlook.com>
On Fri, Jun 06, 2025 at 08:32:35AM +0000, Chen, Jiqian wrote:
> On 2025/6/5 23:14, Roger Pau Monné wrote:
> > On Mon, May 26, 2025 at 05:45:57PM +0800, Jiqian Chen wrote:
> >> When init_rebar() fails, current logic return fail and free Rebar-related
> >> resources in vpci_deassign_device(). But the previous new changes will
> >> hide Rebar capability and return success, it can't reach
> >> vpci_deassign_device() to remove resources if hiding success, so those
> >> resources must be removed in cleanup function of Rebar.
> >>
> >> To do that, implement cleanup function for Rebar.
> >>
> >> Signed-off-by: Jiqian Chen <Jiqian.Chen@amd.com>
> >
> > LGTM, just one nit about a bounds check.
> >
> >> ---
> >> cc: "Roger Pau Monné" <roger.pau@citrix.com>
> >> ---
> >> v4->v5 changes:
> >> * Change definition "static void cleanup_rebar" to "static int cf_check cleanup_rebar" since cleanup hook is changed to be int.
> >>
> >> v3->v4 changes:
> >> * Change function name from fini_rebar() to cleanup_rebar().
> >> * Change the error number to be E2BIG and ENXIO in init_rebar().
> >>
> >> 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 9cafd80ca2c9..4b1892fab3d6 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 int cf_check cleanup_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) )
> >
> > I think you could check rebar_offset < PCI_CFG_SPACE_SIZE to be more
> > accurate?
> OK.
> Do I need to change in init_rebar()?
Hm, pci_find_ext_capability() will never return a value <
PCI_CFG_SPACE_SIZE different than 0, so maybe none of this is needed.
Just leave it like you have, and please ignore the other requests to
change the checks, sorry for the fuss.
Thanks, Roger.
next prev parent reply other threads:[~2025-06-06 9:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 9:45 [PATCH v5 00/10] Support hiding capability when its initialization fails Jiqian Chen
2025-05-26 9:45 ` [PATCH v5 01/10] vpci/header: Move emulating cap list logic into new function Jiqian Chen
2025-05-26 9:45 ` [PATCH v5 02/10] vpci/header: Emulate legacy capability list for dom0 Jiqian Chen
2025-06-05 10:54 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 03/10] vpci/header: Emulate extended " Jiqian Chen
2025-06-05 11:24 ` Roger Pau Monné
2025-06-06 4:05 ` Chen, Jiqian
2025-05-26 9:45 ` [PATCH v5 04/10] vpci: Refactor REGISTER_VPCI_INIT Jiqian Chen
2025-06-05 12:50 ` Roger Pau Monné
2025-06-05 12:59 ` Jan Beulich
2025-06-06 6:29 ` Chen, Jiqian
2025-06-06 7:05 ` Jan Beulich
2025-06-06 9:14 ` Roger Pau Monné
2025-06-09 7:50 ` Chen, Jiqian
2025-06-09 9:29 ` Roger Pau Monné
2025-06-09 10:18 ` Chen, Jiqian
2025-06-09 10:40 ` Roger Pau Monné
2025-06-10 3:52 ` Chen, Jiqian
2025-06-10 7:08 ` Jan Beulich
2025-06-10 9:03 ` Chen, Jiqian
2025-06-11 10:19 ` Chen, Jiqian
2025-06-11 10:57 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 05/10] vpci: Hide legacy capability when it fails to initialize Jiqian Chen
2025-06-05 13:35 ` Roger Pau Monné
2025-06-06 7:03 ` Chen, Jiqian
2025-06-06 9:16 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 06/10] vpci: Hide extended " Jiqian Chen
2025-06-05 14:47 ` Roger Pau Monné
2025-06-06 8:30 ` Chen, Jiqian
2025-06-06 9:18 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 07/10] vpci: Refactor vpci_remove_register to remove matched registers Jiqian Chen
2025-06-05 15:00 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 08/10] vpci/rebar: Free Rebar resources when init_rebar() fails Jiqian Chen
2025-06-05 15:14 ` Roger Pau Monné
2025-06-06 8:32 ` Chen, Jiqian
2025-06-06 9:20 ` Roger Pau Monné [this message]
2025-05-26 9:45 ` [PATCH v5 09/10] vpci/msi: Free MSI resources when init_msi() fails Jiqian Chen
2025-06-05 15:19 ` Roger Pau Monné
2025-06-06 8:38 ` Chen, Jiqian
2025-06-06 9:21 ` Roger Pau Monné
2025-05-26 9:45 ` [PATCH v5 10/10] vpci/msix: Free MSIX resources when init_msix() fails Jiqian Chen
2025-06-05 15:34 ` Roger Pau Monné
2025-06-06 8:44 ` Chen, Jiqian
2025-06-06 9:23 ` Roger Pau Monné
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=aEKy9nt8NNTKHaxo@macbook.local \
--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.