From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Anthony PERARD <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: "xl vcpu-set" not persistent across reboot?
Date: Tue, 14 Jun 2016 18:03:01 +0100 [thread overview]
Message-ID: <20160614170301.GS28116@citrix.com> (raw)
In-Reply-To: <22368.14172.762223.551307@mariner.uk.xensource.com>
On Tue, Jun 14, 2016 at 05:57:00PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: [Xen-devel] "xl vcpu-set" not persistent across reboot?"):
> > What Andrew means is that QEMU shouldn't have kept the CPU state
> > structures in the first place. My response explains why that is not
> > possible from a QEMU upstream point of view.
>
> I don't think it addresses my point.
>
> > Hence the unfortunate fact is that we need to live with it for now. To
> > start QEMU we need to create a bunch of dummy CPUs to keep QEMU happy.
> > All those dummy states need to be kept.
>
> Why do we need one dummy state per actual vcpu rather than just one
> dummy state no matter how many vcpus ?
>
We can't because ...
> Or is qemu involved in hvm cpu hotplug ?
>
when doing hotplug, libxl uses QMP command to tell QEMU to create
CPUs.
Whether this can be changed I will let Anthony and Stefano to answer.
Wei.
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-14 17:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 8:29 "xl vcpu-set" not persistent across reboot? Jan Beulich
2016-06-03 13:41 ` Wei Liu
2016-06-03 14:42 ` Jan Beulich
2016-06-03 16:35 ` Wei Liu
2016-06-06 8:58 ` Jan Beulich
2016-06-06 17:18 ` Wei Liu
2016-06-06 17:20 ` Wei Liu
2016-06-06 17:34 ` Andrew Cooper
2016-06-07 8:30 ` Wei Liu
2016-06-14 16:34 ` Ian Jackson
2016-06-14 16:39 ` Wei Liu
2016-06-14 16:57 ` Ian Jackson
2016-06-14 16:59 ` Andrew Cooper
2016-06-14 17:06 ` Wei Liu
2016-06-14 17:03 ` Wei Liu [this message]
2016-06-14 17:23 ` Wei Liu
2016-06-14 17:35 ` Anthony PERARD
2016-06-07 6:38 ` Jan Beulich
2016-06-07 8:27 ` Wei Liu
2016-06-06 9:04 Jan Beulich
2016-06-06 13:07 ` Stefano Stabellini
2016-06-06 13:42 ` Wei Liu
2016-06-06 14:00 ` Stefano Stabellini
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=20160614170301.GS28116@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.jackson@eu.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 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).