From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony.Perard@citrix.com, xen-devel@lists.xensource.com
Subject: Re: request for a release-ack on qemu-xen
Date: Thu, 20 Feb 2014 16:23:18 +0000 [thread overview]
Message-ID: <53062BF6.50303@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402201452550.15812@kaball.uk.xensource.com>
On 02/20/2014 02:56 PM, Stefano Stabellini wrote:
> Hi George,
> the following two commits in qemu-xen:
>
> commit 65fc9b78ba3d868a26952db0d8e51cecf01d47b4
> Author: Anthony PERARD <anthony.perard@citrix.com>
> Date: Wed Sep 25 16:43:12 2013 +0000
>
> xen: Enable cpu-hotplug on xenfv machine.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> Conflicts:
> hw/i386/pc_piix.c
>
> commit 29a757f0fce7bfdf965d9e8ea48e8e34f997a32c
> Author: Anthony PERARD <anthony.perard@citrix.com>
> Date: Wed Sep 25 16:41:48 2013 +0000
>
> xen: Fix vcpu initialization.
>
> Each vcpu need a evtchn binded in qemu, even those that are
> offline at QEMU initialisation.
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> were already present in the tree and fix cpu-hotplug.
> One of the latest merges from the QEMU 1.6 stable tree effectively
> reverted them. May I have a release exception to push them back in?
> Without them cpu-hotplug does not work.
It looks like this touches vcpu initialization, which is pretty core to
the functionality of a VM as a whole. Hotplug, on the other hand, while
an important feature, is much less commonly used.
Given that we're hoping to have an RC5 tomorrow and tag a release next
week, I think I'd rather these wait until 4.4.1.
-George
prev parent reply other threads:[~2014-02-20 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 14:56 request for a release-ack on qemu-xen Stefano Stabellini
2014-02-20 16:23 ` George Dunlap [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=53062BF6.50303@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Anthony.Perard@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.