From: David Vrabel <dvrabel@cantab.net>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: xen-devel@lists.xenproject.org, Andrew Jones <drjones@redhat.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH v3 0/1] Introduce VCPUOP_reset_vcpu_info
Date: Tue, 19 Aug 2014 19:59:52 +0100 [thread overview]
Message-ID: <53F39EA8.5020602@cantab.net> (raw)
In-Reply-To: <1408442683-12125-1-git-send-email-vkuznets@redhat.com>
On 19/08/14 11:04, Vitaly Kuznetsov wrote:
> The patch and guest code are based on the prototype by Konrad Rzeszutek Wilk.
>
> VCPUOP_reset_vcpu_info is required to support kexec performed by smp pvhvm
> guest. It was tested with the guest code listed below.
Instead of having the guest teardown all these bits of setup. I think
it would be preferable to have the toolstack build a new domain with the
same memory contents from the original VM. The toolstack would then
start this new domain at the kexec entry point.
The advantage of this is you don't need to add new hypercall sub-ops to
teardown all bits and pieces, both for existing stuff and for anything
new that might be added.
David
next prev parent reply other threads:[~2014-08-19 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 10:04 [PATCH v3 0/1] Introduce VCPUOP_reset_vcpu_info Vitaly Kuznetsov
2014-08-19 10:04 ` [PATCH v3 1/1] " Vitaly Kuznetsov
2014-08-19 10:21 ` Andrew Cooper
2014-08-19 23:22 ` Jan Beulich
2014-08-19 18:59 ` David Vrabel [this message]
2014-08-20 8:43 ` [PATCH v3 0/1] " Vitaly Kuznetsov
2014-08-20 13:37 ` Konrad Rzeszutek Wilk
2014-08-20 21:57 ` Konrad Rzeszutek Wilk
2014-08-21 10:35 ` Vitaly Kuznetsov
2014-08-22 2:27 ` Konrad Rzeszutek Wilk
2014-08-22 9:08 ` Jan Beulich
2014-08-22 12:41 ` David Vrabel
2014-08-22 13:23 ` Jan Beulich
2014-08-25 13:50 ` Vitaly Kuznetsov
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=53F39EA8.5020602@cantab.net \
--to=dvrabel@cantab.net \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=drjones@redhat.com \
--cc=vkuznets@redhat.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.