From: Olaf Hering <olaf@aepfle.de>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Andrew Jones <drjones@redhat.com>,
Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 0/9] toolstack-based approach to pvhvm guest kexec
Date: Thu, 11 Dec 2014 15:24:28 +0100 [thread overview]
Message-ID: <20141211142428.GA19820@aepfle.de> (raw)
In-Reply-To: <1417626981-8432-1-git-send-email-vkuznets@redhat.com>
On Wed, Dec 03, Vitaly Kuznetsov wrote:
> When a PVHVM linux guest performs kexec there are lots of things which
> require taking care of:
> - shared info, vcpu_info
> - grants
> - event channels
> - ...
> Instead of taking care of all these things we can rebuild the domain
> performing kexec from scratch doing so-called soft-reboot.
How does this approach handle ballooned pages?
>From the guests point of view they are always there, just claimed by the
balloon driver. The new kernel does not have that driver nor does its
driver have the knowledge which pages the old kernel gave back to Xen.
After a brief look none of the patches seem to deal with that.
Olaf
next prev parent reply other threads:[~2014-12-11 14:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 17:16 [PATCH v4 0/9] toolstack-based approach to pvhvm guest kexec Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 1/9] xen: introduce DOMDYING_locked state Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 2/9] xen: introduce SHUTDOWN_soft_reset shutdown reason Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 3/9] libxl: support " Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 4/9] xen: introduce XEN_DOMCTL_devour Vitaly Kuznetsov
2014-12-04 0:50 ` Julien Grall
2014-12-04 10:19 ` David Vrabel
2014-12-04 10:52 ` Julien Grall
2014-12-04 15:12 ` Vitaly Kuznetsov
2014-12-04 15:54 ` Julien Grall
2014-12-04 11:01 ` Julien Grall
2014-12-04 14:48 ` Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 5/9] libxc: support XEN_DOMCTL_devour Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 6/9] libxl: add libxl__domain_soft_reset_destroy_old() Vitaly Kuznetsov
2014-12-04 16:20 ` Wei Liu
2014-12-03 17:16 ` [PATCH v4 7/9] libxc: introduce soft reset for HVM domains Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 8/9] libxl: soft reset support Vitaly Kuznetsov
2014-12-04 16:01 ` Wei Liu
2014-12-05 10:45 ` Vitaly Kuznetsov
2014-12-03 17:16 ` [PATCH v4 9/9] xsm: add XEN_DOMCTL_devour support Vitaly Kuznetsov
2014-12-04 11:17 ` [PATCH v4 0/9] toolstack-based approach to pvhvm guest kexec Olaf Hering
2014-12-04 14:29 ` Vitaly Kuznetsov
2014-12-04 11:55 ` Wei Liu
2014-12-04 14:46 ` Vitaly Kuznetsov
2014-12-04 15:08 ` Wei Liu
2014-12-11 14:24 ` Olaf Hering [this message]
2014-12-11 15:24 ` David Vrabel
2014-12-11 15:30 ` Olaf Hering
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=20141211142428.GA19820@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=drjones@redhat.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vkuznets@redhat.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.