All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Andrew Jones <drjones@redhat.com>,
	Julien Grall <julien.grall@linaro.org>,
	Wei Liu <wei.liu2@citrix.com>,
	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, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v5 0/9] toolstack-based approach to pvhvm guest kexec
Date: Wed, 7 Jan 2015 10:10:57 +0100	[thread overview]
Message-ID: <20150107091057.GA12049@aepfle.de> (raw)
In-Reply-To: <87r3v9pekz.fsf@vitty.brq.redhat.com>

On Mon, Jan 05, Vitaly Kuznetsov wrote:

> Wei Liu <wei.liu2@citrix.com> writes:
> 
> > Olaf mentioned his concern about handling ballooned pages in
> > <20141211153029.GA1772@aepfle.de>. Is that point moot now?
> 
> Well, the limitation is real and some guest-side handling will be
> required in case we want to support kexec with ballooning. But as David
> validly mentioned "It's the responsibility of the guest to ensure it
> either doesn't kexec when it is ballooned or that the kexec kernel can
> handle this". Not sure if we can (and need to) do anything hypevisor- or
> toolstack-side.

One approach would be to mark all pages as some sort of
populate-on-demand first. Then copy the existing assigned pages from
domA to domB and update the page type. The remaining pages are likely
ballooned. Once the guest tries to access them this should give the
hypervisor and/or toolstack a chance to assign a real RAM page to them.

I mean, if a host-assisted approach for kexec is implemented then this
approach must also cover ballooning.


Olaf

  reply	other threads:[~2015-01-07  9:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 13:45 [PATCH v5 0/9] toolstack-based approach to pvhvm guest kexec Vitaly Kuznetsov
2014-12-11 13:45 ` [PATCH v5 1/9] xen: introduce DOMDYING_locked state Vitaly Kuznetsov
2014-12-18 13:23   ` Jan Beulich
2014-12-11 13:45 ` [PATCH v5 2/9] xen: introduce SHUTDOWN_soft_reset shutdown reason Vitaly Kuznetsov
2014-12-18 13:28   ` Jan Beulich
2015-01-13 12:20   ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 3/9] libxl: support " Vitaly Kuznetsov
2015-01-13 12:22   ` Ian Campbell
2015-01-13 12:23   ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 4/9] xen: introduce XEN_DOMCTL_devour Vitaly Kuznetsov
2014-12-18 13:57   ` Jan Beulich
2015-01-13 12:26     ` Ian Campbell
2015-01-13 13:53   ` Ian Campbell
2015-01-13 14:48     ` Tim Deegan
2015-01-13 16:17     ` Vitaly Kuznetsov
2015-01-13 16:24       ` Jan Beulich
2015-01-13 16:45         ` Vitaly Kuznetsov
2015-01-13 16:56           ` Jan Beulich
2015-01-13 16:41       ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 5/9] libxc: support XEN_DOMCTL_devour Vitaly Kuznetsov
2014-12-11 13:45 ` [PATCH v5 6/9] libxl: add libxl__domain_soft_reset_destroy() Vitaly Kuznetsov
2015-01-13 13:58   ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 7/9] libxc: introduce soft reset for HVM domains Vitaly Kuznetsov
2015-01-13 14:08   ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 8/9] libxl: soft reset support Vitaly Kuznetsov
2015-01-13 14:21   ` Ian Campbell
2014-12-11 13:45 ` [PATCH v5 9/9] xsm: add XEN_DOMCTL_devour support Vitaly Kuznetsov
2014-12-18 13:59   ` Jan Beulich
2015-01-05 12:46 ` [PATCH v5 0/9] toolstack-based approach to pvhvm guest kexec Wei Liu
2015-01-05 13:00   ` Vitaly Kuznetsov
2015-01-07  9:10     ` Olaf Hering [this message]
2015-01-07 10:41       ` David Vrabel
2015-01-07 10:54         ` Jan Beulich
2015-01-07 11:59           ` Vitaly Kuznetsov
2015-01-07 11:01         ` Olaf Hering
2015-01-13 12:18         ` Ian Campbell
2015-01-07 10:49       ` Vitaly Kuznetsov
2015-01-07 11:03         ` Olaf Hering
2015-01-14 11:06           ` George Dunlap

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=20150107091057.GA12049@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=julien.grall@linaro.org \
    --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.