From: "Jan Beulich" <JBeulich@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH v2 3/3] libxl: only issue cpu-add call to QEMU for not present CPU
Date: Wed, 08 Jun 2016 09:01:12 -0600 [thread overview]
Message-ID: <57584F5802000078000F3313@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1465396126-27426-4-git-send-email-wei.liu2@citrix.com>
>>> On 08.06.16 at 16:28, <wei.liu2@citrix.com> wrote:
> Calculate the final bitmap for CPUs to add to avoid having annoying
> error messages complaining those CPUs are already present.
Ah, nice - I had noticed these odd errors too, but didn't dare to
complain about such a cosmetic issue at the same time.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-08 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 14:28 [PATCH v2 0/3] libxl: libxl: update available vcpus map in retrieve configuration function Wei Liu
2016-06-08 14:28 ` [PATCH v2 1/3] libxl: introduce libxl__qmp_query_cpus Wei Liu
2016-06-09 0:12 ` Dario Faggioli
2016-06-13 16:52 ` Anthony PERARD
2016-06-13 18:17 ` Wei Liu
2016-06-08 14:28 ` [PATCH v2 2/3] libxl: update vcpus bitmap in retrieved guest config Wei Liu
2016-06-09 0:11 ` Dario Faggioli
2016-06-13 17:39 ` Anthony PERARD
2016-06-13 18:21 ` Wei Liu
2016-06-14 10:47 ` Anthony PERARD
2016-06-14 10:50 ` Wei Liu
2016-06-14 10:58 ` Anthony PERARD
2016-06-14 11:00 ` Wei Liu
2016-06-14 16:27 ` Ian Jackson
2016-06-14 13:20 ` Anthony PERARD
2016-06-08 14:28 ` [PATCH v2 3/3] libxl: only issue cpu-add call to QEMU for not present CPU Wei Liu
2016-06-08 15:01 ` Jan Beulich [this message]
2016-06-13 17:47 ` Anthony PERARD
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=57584F5802000078000F3313@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).