From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Juergen Gross" <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 6/7] tools/libs: add a new libxenmanage library
Date: Mon, 16 Dec 2024 14:49:25 +0000 [thread overview]
Message-ID: <Z2A99DaztQH9161h@l14> (raw)
In-Reply-To: <20241213162421.16782-7-jgross@suse.com>
On Fri, Dec 13, 2024 at 05:24:20PM +0100, Juergen Gross wrote:
> diff --git a/tools/include/xenmanage.h b/tools/include/xenmanage.h
> new file mode 100644
> index 0000000000..5d169693b0
> --- /dev/null
> +++ b/tools/include/xenmanage.h
> @@ -0,0 +1,92 @@
> +/* SPDX-License-Identifier: LGPL-2.1 */
This should read "LGPL-2.1-only".
> diff --git a/tools/libs/manage/core.c b/tools/libs/manage/core.c
> new file mode 100644
> index 0000000000..b5fa67b036
> --- /dev/null
> +++ b/tools/libs/manage/core.c
> @@ -0,0 +1,168 @@
> +static int xenmanage_do_domctl_get_domain_state(xenmanage_handle *hdl,
> + unsigned int domid_in,
> + unsigned int *domid_out,
> + unsigned int *state,
> + uint64_t *unique_id)
> +{
> + struct xen_domctl *buf;
> + int saved_errno;
> + int ret;
> +
> + buf = xencall_alloc_buffer(hdl->xcall, sizeof(*buf));
> + if ( !buf )
> + {
> + errno = ENOMEM;
Is this necessary? Isn't xencall_alloc_buffer() going to set `errno`? Or
is it to overwrite `errno` set by system calls which could be other than
ENOMEM?
> + return -1;
> + }
Otherwise, patch looks fine to me: Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>
Thanks,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2024-12-16 14:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:24 [PATCH v3 0/7] remove libxenctrl usage from xenstored Juergen Gross
2024-12-13 16:24 ` [PATCH v3 1/7] xen/xsm: make getdomaininfo xsm dummy checks more stringent Juergen Gross
2024-12-13 16:24 ` [PATCH v3 2/7] tools: add a dedicated header file for barrier definitions Juergen Gross
2024-12-16 14:14 ` Anthony PERARD
2024-12-13 16:24 ` [PATCH v3 3/7] xen: add a domain unique id to each domain Juergen Gross
2024-12-13 16:24 ` [PATCH v3 4/7] xen: add bitmap to indicate per-domain state changes Juergen Gross
2024-12-16 10:21 ` Jan Beulich
2024-12-16 13:30 ` Jürgen Groß
2024-12-13 16:24 ` [PATCH v3 5/7] xen: add new domctl get_changed_domain Juergen Gross
2024-12-16 10:41 ` Jan Beulich
2024-12-16 13:57 ` Jürgen Groß
2024-12-16 15:03 ` Juergen Gross
2024-12-16 15:18 ` Jan Beulich
2024-12-16 15:20 ` Jürgen Groß
2024-12-13 16:24 ` [PATCH v3 6/7] tools/libs: add a new libxenmanage library Juergen Gross
2024-12-16 14:49 ` Anthony PERARD [this message]
2024-12-16 15:15 ` Juergen Gross
2024-12-13 16:24 ` [PATCH v3 7/7] tools/xenstored: use new stable interface instead of libxenctrl Juergen Gross
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=Z2A99DaztQH9161h@l14 \
--to=anthony.perard@vates.tech \
--cc=jgross@suse.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.