From: Paul Durrant <xadimgnik@gmail.com>
To: Julien Grall <julien@xen.org>, xen-devel@lists.xenproject.org
Cc: dwmw2@infradead.org, hongyxia@amazon.com, raphning@amazon.com,
maghul@amazon.com, Julien Grall <jgrall@amazon.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH RFC 2/2] xen/kexec: Reserve KEXEC_TYPE_LIVEUPDATE and KEXEC_RANGE_MA_LIVEUPDATE
Date: Fri, 7 May 2021 08:59:16 +0100 [thread overview]
Message-ID: <a2fcd673-2500-917e-16f2-d18e553fe2db@xen.org> (raw)
In-Reply-To: <20210506104259.16928-3-julien@xen.org>
On 06/05/2021 11:42, Julien Grall wrote:
> From: Julien Grall <jgrall@amazon.com>
>
> Unfortunately, the code to support Live Update has already been merged in
> Kexec and shipped since 2.0.21. Reserve the IDs used by Kexec before they
> end up to be re-used for a different purpose.
>
> This patch reserves two IDs:
> * KEXEC_TYPE_LIVEUPDATE: New operation to request Live Update
> * KEXEC_MA_RANGE_LIVEUPDATE: New range to query the Live Update
> area below Xen
>
> Signed-off-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Paul Durrant <paul@xen.org>
> ---
> xen/include/public/kexec.h | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/xen/include/public/kexec.h b/xen/include/public/kexec.h
> index 3f2a118381ba..650d2feb036f 100644
> --- a/xen/include/public/kexec.h
> +++ b/xen/include/public/kexec.h
> @@ -71,17 +71,22 @@
> */
>
> /*
> - * Kexec supports two types of operation:
> + * Kexec supports three types of operation:
> * - kexec into a regular kernel, very similar to a standard reboot
> * - KEXEC_TYPE_DEFAULT is used to specify this type
> * - kexec into a special "crash kernel", aka kexec-on-panic
> * - KEXEC_TYPE_CRASH is used to specify this type
> * - parts of our system may be broken at kexec-on-panic time
> * - the code should be kept as simple and self-contained as possible
> + * - Live update into a new Xen, preserving all running domains
> + * - KEXEC_TYPE_LIVE_UPDATE is used to specify this type
> + * - Xen performs non-cooperative live migration and stores live
> + * update state in memory, passing it to the new Xen.
> */
>
> -#define KEXEC_TYPE_DEFAULT 0
> -#define KEXEC_TYPE_CRASH 1
> +#define KEXEC_TYPE_DEFAULT 0
> +#define KEXEC_TYPE_CRASH 1
> +#define KEXEC_TYPE_LIVEUPDATE 2
>
>
> /* The kexec implementation for Xen allows the user to load two
> @@ -150,6 +155,8 @@ typedef struct xen_kexec_load_v1 {
> #define KEXEC_RANGE_MA_EFI_MEMMAP 5 /* machine address and size of
> * of the EFI Memory Map */
> #define KEXEC_RANGE_MA_VMCOREINFO 6 /* machine address and size of vmcoreinfo */
> +/* machine address and size of the Live Update area below Xen */
> +#define KEXEC_RANGE_MA_LIVEUPDATE 7
>
> /*
> * Find the address and size of certain memory areas
>
next prev parent reply other threads:[~2021-05-07 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 10:42 [PATCH RFC 0/2] Add a design document for Live Updating Xen Julien Grall
2021-05-06 10:42 ` [PATCH RFC 1/2] docs/design: Add a design document for Live Update Julien Grall
2021-05-06 14:43 ` Paul Durrant
2021-05-07 9:18 ` Hongyan Xia
2021-05-07 10:00 ` Julien Grall
2021-05-07 9:52 ` Jan Beulich
2021-05-07 11:44 ` Julien Grall
2021-05-07 12:15 ` Jan Beulich
2021-05-07 14:59 ` Xia, Hongyan
2021-05-07 15:28 ` Jan Beulich
2021-05-06 10:42 ` [PATCH RFC 2/2] xen/kexec: Reserve KEXEC_TYPE_LIVEUPDATE and KEXEC_RANGE_MA_LIVEUPDATE Julien Grall
2021-05-07 7:59 ` Paul Durrant [this message]
2021-05-07 8:24 ` Hongyan Xia
2021-05-07 8:30 ` Jan Beulich
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=a2fcd673-2500-917e-16f2-d18e553fe2db@xen.org \
--to=xadimgnik@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw2@infradead.org \
--cc=george.dunlap@citrix.com \
--cc=hongyxia@amazon.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=maghul@amazon.com \
--cc=paul@xen.org \
--cc=raphning@amazon.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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).