All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anthony PERARD" <anthony.perard@vates.tech>
To: dmukhin@ford.com
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
	jbeulich@suse.com, julien@xen.org, michal.orzel@amd.com,
	roger.pau@citrix.com, sstabellini@kernel.org
Subject: Re: [PATCH v6] xen/domain: introduce DOMID_ANY
Date: Mon, 09 Mar 2026 12:22:06 +0000	[thread overview]
Message-ID: <aa67bEWug18FDYwY@l14> (raw)
In-Reply-To: <20260307025451.3148078-2-dmukhin@ford.com>

On Fri, Mar 06, 2026 at 06:54:52PM -0800, dmukhin@ford.com wrote:
> diff --git a/tools/libs/light/libxl_create.c b/tools/libs/light/libxl_create.c
> index bfc9149096a3..79af2958d170 100644
> --- a/tools/libs/light/libxl_create.c
> +++ b/tools/libs/light/libxl_create.c
> @@ -666,7 +666,7 @@ int libxl__domain_make(libxl__gc *gc, libxl_domain_config *d_config,
>          }
>  
>          for (;;) {
> -            uint32_t local_domid;
> +            uint32_t local_domid = DOMID_INVALID;

Surely, this change is unnecessary?

>              bool recent;
>  
>              if (info->domid == RANDOM_DOMID) {
> @@ -681,8 +681,10 @@ int libxl__domain_make(libxl__gc *gc, libxl_domain_config *d_config,
>                      continue;
>  
>                  local_domid = v;
> +            } else if (libxl_domid_valid_guest(local_domid)) {

You meant to check `info->domid`, right?

> +                local_domid = info->domid;
>              } else {
> -                local_domid = info->domid; /* May not be valid */
> +                local_domid = DOMID_ANY;
>              }

Cheers,


--
Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech



      reply	other threads:[~2026-03-09 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  2:54 [PATCH v6] xen/domain: introduce DOMID_ANY dmukhin
2026-03-09 12:22 ` Anthony PERARD [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=aa67bEWug18FDYwY@l14 \
    --to=anthony.perard@vates.tech \
    --cc=andrew.cooper3@citrix.com \
    --cc=dmukhin@ford.com \
    --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.