All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Jan Beulich" <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/page_alloc: Simplify domain_adjust_tot_pages
Date: Thu, 27 Feb 2025 14:59:56 +0000	[thread overview]
Message-ID: <D83BG5T2IRZW.2J68RYJ8CFPY6@cloud.com> (raw)
In-Reply-To: <fde4d70e-d7af-4e51-a871-d4ac19737064@suse.com>

On Wed Feb 26, 2025 at 2:02 PM GMT, Jan Beulich wrote:
> On 24.02.2025 14:27, Alejandro Vallejo wrote:
> > @@ -504,17 +502,16 @@ unsigned long domain_adjust_tot_pages(struct domain *d, long pages)
> >          goto out;
> >  
> >      spin_lock(&heap_lock);
> > -    /* adjust domain outstanding pages; may not go negative */
> > -    dom_before = d->outstanding_pages;
> > -    dom_after = dom_before - pages;
> > -    BUG_ON(dom_before < 0);
> > -    dom_claimed = dom_after < 0 ? 0 : dom_after;
> > -    d->outstanding_pages = dom_claimed;
> > -    /* flag accounting bug if system outstanding_claims would go negative */
> > -    sys_before = outstanding_claims;
> > -    sys_after = sys_before - (dom_before - dom_claimed);
> > -    BUG_ON(sys_after < 0);
> > -    outstanding_claims = sys_after;
> > +    BUG_ON(outstanding_claims < d->outstanding_pages);
> > +    if ( pages > 0 && d->outstanding_pages < pages )
>
> The lhs isn't needed, is it? d->outstanding_pages is an unsigned quantity,
> after all. Else dropping the earlier of the two BUG_ON() wouldn't be quite
> right.

d->outstanding pages is unsigned, but pages isn't.

It was originally like that, but I then got concerned about 32bit machines,
where you'd be comparing a signed and an unsigned integer of the same
not-very-large width. That seems like dangerous terrains if the unsigned number
grows large enough.

TL;DR: It's there for clarity and paranoia. Even if the overflowing into bit 31
would be rare in such a system.

>
> > +    {
> > +        /* `pages` exceeds the domain's outstanding count. Zero it out. */
> > +        outstanding_claims -= d->outstanding_pages;
> > +        d->outstanding_pages = 0;
> > +    } else {
>
> Nit: Braces on their own lines please.

Ack.

>
> In any event - yes, this reads quite a bit easier after the adjustment.
>
> With the adjustments (happy to make while committing, so long as you agree)
> Reviewed-by: Jan Beulich <jbeulich@suse.com>

Thanks. I'd probably like to hold off and send a v2 if you're fine with the
adjustment I answered Roger with (returning ealy on pages <= 0, so claims are
never increased on free).

>
> Jan
>

Cheers,
Alejandro


  reply	other threads:[~2025-02-27 15:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 13:27 [PATCH] xen/page_alloc: Simplify domain_adjust_tot_pages Alejandro Vallejo
2025-02-24 14:49 ` Alejandro Vallejo
2025-02-26 14:05   ` Jan Beulich
2025-02-27 14:36     ` Alejandro Vallejo
2025-03-05 10:49       ` Jan Beulich
2025-03-05 13:22         ` Alejandro Vallejo
2025-03-05 13:39           ` Jan Beulich
2025-03-05 14:55             ` Alejandro Vallejo
2025-03-11  9:46             ` Alejandro Vallejo
2025-03-11 10:06               ` Jan Beulich
2025-02-26 14:18   ` Roger Pau Monné
2025-02-26 13:56 ` Roger Pau Monné
2025-02-26 14:08   ` Jan Beulich
2025-02-26 14:28     ` Roger Pau Monné
2025-02-26 14:36       ` Jan Beulich
2025-02-26 16:04         ` Roger Pau Monné
2025-02-26 16:06           ` Jan Beulich
2025-02-26 16:34             ` Andrew Cooper
2025-02-26 16:42               ` Jan Beulich
2025-02-26 16:51                 ` Andrew Cooper
2025-02-27 14:39                   ` Alejandro Vallejo
2025-02-27 14:50       ` Alejandro Vallejo
2025-03-05 10:50         ` Jan Beulich
2025-02-26 14:02 ` Jan Beulich
2025-02-27 14:59   ` Alejandro Vallejo [this message]
2025-03-05 10:52     ` Jan Beulich

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=D83BG5T2IRZW.2J68RYJ8CFPY6@cloud.com \
    --to=alejandro.vallejo@cloud.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --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.