From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>, xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
Ian Jackson <ian.jackson@citrix.com>,
Wei Liu <wei.liu2@citrix.com>, Ronald Rojas <ronladred@gmail.com>
Subject: Re: [PATCH 1/2] tools/libxc: Introduce XC_CPUPOOL_POOLID_ANY
Date: Wed, 8 Feb 2017 17:03:04 +0100 [thread overview]
Message-ID: <1486569784.3042.0.camel@citrix.com> (raw)
In-Reply-To: <1486565506-8541-1-git-send-email-george.dunlap@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]
On Wed, 2017-02-08 at 14:51 +0000, George Dunlap wrote:
> Callers to xc_cpupool_create() can either request a specific pool id,
> or request that Xen do it for them. But at the moment, the
> "automatic" selection is indicated by using a magic value, 0. This
> is
> undesirable both because it doesn't obviously have meaning, but also
> because '0' is a valid cpupool (albeit one which at the moment can't
> be changed).
>
> Introduce a constant, XC_CPUPOOL_POOLID_ANY, to indicate this
> instead.
> Have it be the default for the python bindings.
>
> Manually translate it, even though it's the same underlying value,
> because we don't yet have a relaible way of enforcing that these
> values are the same.
>
> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-08 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 14:51 [PATCH 1/2] tools/libxc: Introduce XC_CPUPOOL_POOLID_ANY George Dunlap
2017-02-08 14:51 ` [PATCH 2/2] tools/libxl: Introduce LIBXL_CPUPOOL_POOLID_ANY George Dunlap
2017-02-08 16:11 ` Dario Faggioli
2017-02-08 16:17 ` George Dunlap
2017-02-09 10:35 ` Wei Liu
2017-02-09 11:17 ` George Dunlap
2017-02-09 11:24 ` Wei Liu
2017-02-09 11:35 ` George Dunlap
2017-02-14 10:29 ` Wei Liu
2017-02-14 12:23 ` George Dunlap
2017-02-08 16:03 ` Dario Faggioli [this message]
2017-02-09 10:36 ` [PATCH 1/2] tools/libxc: Introduce XC_CPUPOOL_POOLID_ANY Wei Liu
2017-02-14 16:57 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2017-02-15 17:08 George Dunlap
2017-02-16 13:02 ` Wei Liu
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=1486569784.3042.0.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jgross@suse.com \
--cc=ronladred@gmail.com \
--cc=wei.liu2@citrix.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.