All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Ariadne Conill <ariadne@ariadne.space>,
	Stewart Hildebrand <stewart.hildebrand@amd.com>,
	Steven Noonan <steven@edera.dev>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/vpci: do not use pci_sanitize_bar_memory for domU
Date: Wed, 4 Mar 2026 16:32:11 +0100	[thread overview]
Message-ID: <aahQe_rQlBrjQlCh@macbook.local> (raw)
In-Reply-To: <1d832f36-d22e-42c6-996c-d09c06376b8b@suse.com>

On Wed, Feb 25, 2026 at 04:44:09PM +0100, Jan Beulich wrote:
> On 25.02.2026 00:12, Ariadne Conill wrote:
> > From: Steven Noonan <steven@edera.dev>
> > 
> > This function should only be used for the hardware domain, because it
> > compares addresses against the host e820 map.
> 
> The same is true for its sibling function, pci_check_bar(). For both the
> question is whether skipping is the right thing, or whether for DomU-s
> checking against their memory map is what is needed instead.

Well, the usage of pci_check_bar() from modify_bars() is slightly
different: it does get called with the BAR host addresses (not the
guest ones).  So the check will work as expected, albeit given a domU
cannot change the BAR host addresses the check is likely redundant,
but not strictly wrong.

Checking against the memory map for domUs would be complicated, as the
guest can play many games with that memory map.

> > --- a/xen/drivers/vpci/header.c
> > +++ b/xen/drivers/vpci/header.c
> > @@ -394,13 +394,15 @@ static int modify_bars(const struct pci_dev *pdev, uint16_t cmd, bool rom_only)
> >              }
> >          }
> >  
> > -        rc = pci_sanitize_bar_memory(bar->mem);
> > -        if ( rc )
> > -        {
> > -            gprintk(XENLOG_WARNING,
> > -                    "%pp: failed to sanitize BAR#%u memory: %d\n",
> > -                    &pdev->sbdf, i, rc);
> > -            return rc;
> > +        if (is_hardware_domain(pdev->domain)) {
> 
> Nit: Style (see surrounding code you alter).
> 
> > +            rc = pci_sanitize_bar_memory(mem);
> > +            if ( rc )
> > +            {
> > +                gprintk(XENLOG_WARNING,
> > +                        "%pp: failed to sanitize BAR#%u memory: %d\n",
> > +                        &pdev->sbdf, i, rc);
> > +                return rc;
> > +            }
> 
> To avoid the need for re-indentation here (reducing churn) you may want
> to leverage that rc is 0 ahead of the call to pci_sanitize_bar_memory().
> I.e. you could make just the call conditional, without touching anything
> else.

You could also introduce an early continue, and leave the check(s)
below applicable to the hardware domain only.

Thanks, Roger.


      reply	other threads:[~2026-03-04 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 23:12 [PATCH] xen/vpci: do not use pci_sanitize_bar_memory for domU Ariadne Conill
2026-02-25 15:44 ` Jan Beulich
2026-03-04 15:32   ` Roger Pau Monné [this message]

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=aahQe_rQlBrjQlCh@macbook.local \
    --to=roger.pau@citrix.com \
    --cc=ariadne@ariadne.space \
    --cc=jbeulich@suse.com \
    --cc=steven@edera.dev \
    --cc=stewart.hildebrand@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.